-
Notifications
You must be signed in to change notification settings - Fork 764
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
Use match to define which operations a constraint should be applied #2747
Comments
Similar previous discussion: #769 |
Thanks @maxsmythe! Correct, the use case goal is to avoid unnecessary evaluation, so something like you suggest in #769 (comment) would work perfectly. |
Hi @maxsmythe - Circling around, I think we might do something "roughly" equivalent with:
|
Is this in the config resource? |
Yes, I was looking at this example: https://open-policy-agent.github.io/gatekeeper/website/docs/exempt-namespaces |
Gotcha. Yeah, if you want a global exemption, that'd be one way to do it. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
Describe the solution you'd like
I'd like to use
match
to define which operations a constraint should be applied. For example:Some common operations are CREATE, UPDATE, and DELETE. Perhaps Audit could be indicated by
""
or a dedicated value.Cheers!
The text was updated successfully, but these errors were encountered: