-
Notifications
You must be signed in to change notification settings - Fork 674
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
ibm_is_network_acl wrong rules order creation and terraform crash #1117
Comments
We are looking into the issues...Will update the fix |
VaishnaviGopal
added a commit
to VaishnaviGopal/terraform-provider-ibm
that referenced
this issue
Feb 24, 2020
VaishnaviGopal
added a commit
to VaishnaviGopal/terraform-provider-ibm
that referenced
this issue
Feb 24, 2020
hkantare
pushed a commit
that referenced
this issue
Feb 25, 2020
Hey! So it looks like Terraform doesn't crash anymore but the order is still not respected. |
Can you please try with latest releases |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
Terraform Version
Using terraform version v0.12.21 with provider.ibm v1.2.1 and there are some problems working with ACL in VPC gen 1.
Affected Resource(s)
Problem(s):
Actual Behaviour
Problem 1: When creating an ACL the order is not repected (in the example to reproduce it will create the deny rules with priority 1)
Problem 2: Change any value, remove or add an rule on a existing ACL and terraform crash.
Steps to Reproduce
Problem 1: just create the following ACL
Problem 2: modify, add or remove an rule
Panic Output
crash.log
.
The text was updated successfully, but these errors were encountered: