utils/gen_rendered_policies_index.py: read compiled control files #11667
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.
Description:
Rationale:
Control files in the "controls" directory can contain Jinja macros. If a script wants to parse our content with Jinja macros, it requires non-trivial steps to get this working.
The script gen_rendered_policies_index.py is very simple and it reads literarily one key (policy) from the control file. Therefore, it does not care about Jinja at all.
Therefore, it is now reading compiled contro files in the build//controls directory.
This problem was discovered in this PR which added Jinja statements into ANSSI file: #11663
Review Hints:
I think you can review the Github action which builds the web content and compare it with the one present at https://complianceascode.github.io/content-pages/
Or you can do following steps for master and the PR and compare results: