-
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
terraform 0.11.8 - attribute mismatch: credit_specification cpu_credits #5853
Comments
I am having exactly the same issue. Terraform VersionMac OS High Sierra 64bit
Reproducible error as mentioned in the original issue. |
Same issue here
Problem encountered when following the getting started document.
This worked as described. However when changing the AMI and re-applying the template, the reported error occurred. I.e. applying this plan:
Produced the following output and error:
|
The fix for this has been merged into master for the |
This has been released in version 1.37.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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! |
This issue was originally opened by @snimark as hashicorp/terraform#18844. It was migrated here as a result of the provider split. The original body of the issue is below.
I am getting this error message when trying to apply a change to my EC2 instance when trying to invoke a change which requires replacing my EC2.
Terraform Version
Linux 64-bit
Terraform File
Crash Output
File: crash.output.txt
Expected Behavior
According the to the tutorial, running
terraform apply
to change an AWS EC2 should remove the old instance and create a new one to take its place.Actual Behavior
It seems to actually destroy the old instance, but it faults before creating the replacement instance. This behavior is repeatable.
Steps to Reproduce
terraform apply
terraform apply
againThe text was updated successfully, but these errors were encountered: