-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Changing AWS instance type #2365
Comments
Ah yes - we should detect this as "drift" of the instance_type param. Tagged as a bug and pushing a fix now. |
Awesome @phinze. You guys are closing these bugs so fast! |
@phinze not sure if this is actually fixed...? Just had it happen in 0.6.0 |
@phinze ignore me, just noticed the .tf file was out of date, so it was trying to make a legitimate change. false alarm. |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
So I have an instance like this:
I changed the instance type from a c4.large to a c4.xlarge in the console, because terraform wanted to do a delete/create to change the type. I then changed my terraform configuration to c4.xlarge.
When I run terraform plan, it says that it's refreshing the state prior to the plan. But then it doesn't see that the type has already been changed outside terraform and thus wants me to delete/create the instance:
Is this the expected behavior?
The text was updated successfully, but these errors were encountered: