ComplianceAsCode / ComplianceAsCode/content
Build system should give a warning/error when encountering a parametrized rules without its respective variables in a profile
- Dominant language
- Shell
- Stars
- 2.8k
- Forks
- 828
- Avg merge
- 3d 8m
- Merged PRs (30d)
- 80
Description
#### Share the context, Description of the problem
When building a product, some profiles may contain parametrized rules. If the profiles do not also explicitly set the variables for these rules, they rely on some default value. Currently, the build system does not notify the user that the variables are not explicitly set and that default values are used.
When someone wants to add parametrized rules to profiles, it may not be obvious at first that they are parametrized. When the build system does not warn the user about this, it may be overlooked and result in the rules using an undesired value.
#### Proposed change:
There should be a warning or an error issues by the buildsystem when it attempts to build a profile which contains parametrized rules without explicitly set variables. Ideally, the warning should state which rules are affected, what are the IDs of the variables that they use, and perhaps even state the default values that are being used when the variables are not explicitly set.
Contributor guide
Assessment
This issue has not been assessed yet.