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

Authoring Rego rules for constraint template #431

Open
cova-fe opened this issue Sep 20, 2022 · 0 comments
Open

Authoring Rego rules for constraint template #431

cova-fe opened this issue Sep 20, 2022 · 0 comments

Comments

@cova-fe
Copy link

cova-fe commented Sep 20, 2022

Hi all, I'm working on some rego rules for RAM and I have some use cases where the usage of a single

deny [{}] {}, as recommended in current rego rules guide

https://github.com/GoogleCloudPlatform/policy-library/blob/main/docs/constraint_template_authoring.md#write-rego-rule-for-constraint-template

could lead to some complex code.

So I'm wondering why it is not possible to use something like

allow {} 
deny [{ msg1 }] {logic}
deny [{ msg2 }] {logic}

and so on.
As this should be a valid rego approach, is there underlying issue that could prevent this approach?
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant