Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New enforcement level "mandatoryOnCreate" #302

Open
aureq opened this issue Jan 21, 2023 · 0 comments
Open

New enforcement level "mandatoryOnCreate" #302

aureq opened this issue Jan 21, 2023 · 0 comments
Labels
customer/feedback Feedback from customers impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features

Comments

@aureq
Copy link
Member

aureq commented Jan 21, 2023

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

When using Policy-as-Code, a policy have one of the 2 enforcement levels: advisory or mandatory. However, neither may be adequate when a user has many existing resources that aren't compliant but where these legacy resources need to exist as they are (ie, non-compliant) for some time and where new resources will need to be created as well.

To assist with this situation, a new enforcement level mandatoryOnCreate could be added and would behave as follow:

  • If a non-compliant resource already exists and the enforcement level is mandatoryOnCreate, then only a warning is displayed. This is similar to advisory.
  • if a new resource is about to be created and is not compliant with a policy, and that policy has the enforcement level mandatoryOnCreate, then the deployment would be interrupted. This is similar to mandatory.
@aureq aureq added impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features needs-triage Needs attention from the triage team customer/feedback Feedback from customers labels Jan 21, 2023
@Frassle Frassle removed the needs-triage Needs attention from the triage team label Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer/feedback Feedback from customers impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

2 participants