-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
cloudstack_network_acl does not work with projects #6684
Comments
Thanks for the report @serbaut! Unfortunately I cannot reproduce this issue by using the exact same config you provided. So you created a new empty project called If I try that all seems to work as expected and the ACL is not recreated on every |
I can see that "cloudstack_network_acl.foo" is missing from the state file in 0.6.15. Maybe there is some problem with async results not being written to the state file?
|
At https://github.com/hashicorp/terraform/blob/master/builtin/providers/cloudstack/resource_cloudstack_network_acl.go#L94 the acl list is read by id but if the vpc belongs to a project you seem to have to supply the vpcid or projectid for it to return anything?
edit: maybe you are running as admin because then it works. |
I also tried it with a user account, but with the same results... But I guess the problem (and the solution) is clear now :) Thanks and I'll add a PR shortly... |
Fixed by PR #6743 |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
A new cloudstack_network_acl is created each run if the VPC belongs to a project.
Terraform Version
Terraform v0.6.15
CloudStack 4.8
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
No change
Actual Behavior
A new acl list was created.
Steps to Reproduce
terraform apply
terraform apply
The text was updated successfully, but these errors were encountered: