-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
aws_instance.credit_specification: panic: interface conversion: interface {} is nil, not map[string]interface {} #10203
Comments
This is a workaround for terraform-aws-modules#128 and related upstream provider issue, [terraform-aws-provider#10203](hashicorp/terraform-provider-aws#10203).
Patching the terraform-aws-ec2-instance module to make |
…ion` to empty configuration block Reference: #10203 Previously before code fix: ``` === CONT TestAccAWSInstance_CreditSpecification_UnspecifiedToEmpty_NonBurstable panic: interface conversion: interface {} is nil, not map[string]interface {} goroutine 1291 [running]: github.com/terraform-providers/terraform-provider-aws/aws.resourceAwsInstanceUpdate(0xc0004b2460, 0x524ba00, 0xc000b8e480, 0x0, 0x0) /Users/bflad/src/github.com/terraform-providers/terraform-provider-aws-deux/aws/resource_aws_instance.go:1208 +0x485b ``` Output from acceptance testing: ``` --- PASS: TestAccAWSInstance_CreditSpecification_UnspecifiedToEmpty_NonBurstable (135.98s) ```
Fix submitted: #10212 |
The fix for this crash has been merged and will release with version 2.30.0 of the Terraform AWS Provider, later this week. 👍 |
This has been released in version 2.30.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
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
This is an excerpt from
TF_LOG=debug
that is dumped directly after the diff & prompt.Expected Behavior
The aws_instance resource should have successfully been updated or NOOP'd the credit_specification, since this isn't a t2 instance.
Actual Behavior
Steps to Reproduce
Encountered trying to run terraform 0.12 with latest aws provider during migration from 0.11.
terraform apply
Important Factoids
Not that I'm aware of. This is the first-attempt to run an
apply
after migrating our states to 0.12.References
The text was updated successfully, but these errors were encountered: