-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Panic error when creating aws_cloudfront_origin_request_policy: interface {} is nil, not map[string]interface {} #20870
Comments
|
Thanks @ewbankkit . And sorry for creating a duplicated thread. twiden's issue is exactly the same as mine. |
This functionality has been released in v3.65.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Community Note
Terraform CLI and Terraform AWS Provider Version
Terraform v1.0.1 on darwin_arm64
provider registry.terraform.io/hashicorp/aws v3.58.0
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
https://gist.github.com/Lauan/c75f45b971d33813bf7937f16022f4c7
Panic Output
https://gist.github.com/Lauan/c75f45b971d33813bf7937f16022f4c7
Expected Behavior
Creation of the cloudfront origin policy with all behaviors as "none" and no nested blocks
Actual Behavior
It seems to me that the provider is trying to create empty nested blocks, which is not allowed in this context.
Steps to Reproduce
terraform apply
Obs:
terraform plan
works fine, only crashing when applyingImportant Factoids
If you pass non-empty lists for each variable, the resource is created as it should. The issue only happens for empty lists.
Tried to run on my M1 MacBook pro as well as on terraform cloud and the outcome is the same
The text was updated successfully, but these errors were encountered: