-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Cloudfront resource with dynamic blocks and lookup functions fails at first apply #10088
Comments
I guess my issue #12098 is a duplicate of this |
This just occured for us and the only change was an update to the tags on the distribution, the associated buckets and lambda functions |
@grahamhar are you using TF 0.13 and above or not? alot of these issues were solved there, even though there's still some bugs on AWS side especially on the update tags functionality |
@grahamhar we are also encountering this issue, and I am wondering: what did you update exactly in tags? Did you have broken links for example? Really curious, I hope it will work for us as well. |
We simply ran the plan and apply for a second time and it worked which was just as worrying as the error. We upgrade the provider and terraform frequently and have not seen a repeat of this. We're now on terraform 1.0.0 and provider version 3.45.0 |
Hi I am receiving a similar error:
From what I was reading it seems like I might need to add |
I'm receiving exactly the same error as @noahh40 above (
The section from the cloudfront distribution, which seems to trigger it:
and in another place:
I was in the process of upgrading the inline Every 2nd "apply" will run into the issue. I'm using terraform v1.1.7 with aws provider v3.75.1. |
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
The Apply should run without error in first run
Actual Behavior
The Apply fail the first time, but succeed with second run
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: