[BUG] Kantra won't recognize sources/targets exclusive to --rules folder

[jmle]

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

6.0.0.Alpha

Priority

Critical

Current Behavior

When specifying additional rules with --rules, if the contained rules have new sources/targets, they are not recognized by kantra when doing the analysis, and therefore rules are not triggered.

Expected Behavior

Kantra should recognize those sources and targets to be able to run the rules, otherwise they can't be used.

How Reproducible

Always (Default)

Steps To Reproduce

No response

Environment

Any

Anything else?

No response

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

[dymurray]

As a temporary workaround, instead of using --target you can also do --label-selector=konveyor.io/target=foo to get the desired result until this is fixed.

[shawn-hurley]

What do we do today in the non-containerless world? I thought we decided that label selectors are not ever selectively applied and that it was on the user to add the correct labels if they were doing this. The only other option, is to have some sub-system add the always included label for these rules, and that might be possible in the rule parser, but wanted to know what we have today, because I think I could make an argument that this working as expected.