You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
The ability to show/hide policies that passed (i.e. no violations), but that were run, is good from a compliance standpoint. However, the way the Compliance Ready policies implemented this can cause pain:
The problem is that changing the values must be done at the code level, which when using server-side compliance, requires re-publishing the policy pack for what is effectively a config value.
It would be lovely if these options were pushed up to CLI options so that they can be controlled on a per-run basis, which is likely what most customers want. For example, no detailed output in local dev, detailed output in CI/CD (for audit reasons).
Affected area/feature
The text was updated successfully, but these errors were encountered:
Hello!
Issue details
The ability to show/hide policies that passed (i.e. no violations), but that were run, is good from a compliance standpoint. However, the way the Compliance Ready policies implemented this can cause pain:
The problem is that changing the values must be done at the code level, which when using server-side compliance, requires re-publishing the policy pack for what is effectively a config value.
It would be lovely if these options were pushed up to CLI options so that they can be controlled on a per-run basis, which is likely what most customers want. For example, no detailed output in local dev, detailed output in CI/CD (for audit reasons).
Affected area/feature
The text was updated successfully, but these errors were encountered: