-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
google_compute_security_policy - no error message when rule has same priority #5804
google_compute_security_policy - no error message when rule has same priority #5804
Comments
@megan07 after adding a rule in the resource, I got below
|
@edwardmedia , the error is specifically with security policy containing custom rules with Common Expression Language (CEL)
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Terraform v0.12.18
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
Well it should have indicates that two rules with same priority isn't possible, and indicate the rule that didn't create
Actual Behavior
"Apply complete!" No error messages, looks like everything is ok with terraform apply ! => but in google console, only one rule was created
Steps to Reproduce
Create a security policy with 2 rules with the same priority
terraform apply
Important Factoids
This error happen with the security policy using the custom rules:
https://cloud.google.com/armor/docs/rules-language-reference
The text was updated successfully, but these errors were encountered: