Closed jlsan92 closed 4 years ago
Crash fix submitted: https://github.com/terraform-providers/terraform-provider-aws/pull/12614
The underlying plan difference issue with an empty rules
configuration block being added is certainly bizarre, but I wasn't able to reproduce it easily. If that is still happening after this fix on the latest version of the Terraform CLI (0.12.24+), its probably worth opening a new bug report with the prior and updated configurations for reproduction. 👍
The fix mentioned above has been merged and will release with version 2.56.0 of the Terraform AWS Provider, later this week. 👍
This has been released in version 2.56.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 for triage. Thanks!
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!
Community Note
Terraform Version
v0.12.21
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
The S3 bucket replication configuration gets updated.
Actual Behavior
Terraform panic crash
Steps to Reproduce
terraform plan
to see the weird plan result for replication rulesterraform apply
to see the panic errorImportant Factoids
Please note that the plan before applying the changes looks weird in terms of replication rules, there's an empty
rule
config, probably the cause of the crash ⚠️References