You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
terraform apply should not complain about the policy.
Actual Behavior
terraform apply complains about invalid policy on the first run. And then creates ECR policy in the second run.
I have tried to set resource dependencies using depends_on in vain, behavior is same without this parameter.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply (throws an error)
terraform apply (run okay this time)
References
Few other similar issues where terraform does not wait for enough time or AWS reports that the resource creation is complete (a false positive)
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.
ghost
locked and limited conversation to collaborators
Apr 8, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
~$ terraform -v Terraform v0.8.7
Affected Resource(s)
Terraform Configuration Files
Debug Output
First Run
terraform apply
(fails)Second Run
terraform apply
(succeeds)Expected Behavior
terraform apply
should not complain about the policy.Actual Behavior
terraform apply
complains about invalid policy on the first run. And then creates ECR policy in the second run.I have tried to set resource dependencies using
depends_on
in vain, behavior is same without this parameter.Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
(throws an error)terraform apply
(run okay this time)References
Few other similar issues where terraform does not wait for enough time or AWS reports that the resource creation is complete (a false positive)
The text was updated successfully, but these errors were encountered: