Change rule prodtype search and make tests more content change proof #49
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, CTF was taking products only from
prodtype
. That was wrong as it ignored implicit "all products".Now, with ComplianceAsCode/content#11378 prodtype removal, all rules must be part of some profile (at least the
default.profile
) to get to benchmark. And to get to profile, they might get there via controls (that was ignored as well by CTF).This PR adds support for searching rules in control files (works with control_dirs as well) and changes the prodtype search to new approach - products are determined based on used profiles.
Test changes come from #47
For testing, you can for example try:
to check that ocp4 product is selected (the rule introduced in this PR is only in controls file). (related to ComplianceAsCode/content#11501 (comment))