Skip to content
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

Closed
nwalke opened this issue Jun 16, 2015 · 5 comments · Fixed by #2374
Closed

Changing AWS instance type #2365

nwalke opened this issue Jun 16, 2015 · 5 comments · Fixed by #2374

Comments

@nwalke
Copy link
Contributor

nwalke commented Jun 16, 2015

So I have an instance like this:
screen shot 2015-06-16 at 8 52 00 am

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.

screen shot 2015-06-16 at 8 54 35 am

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:
screen shot 2015-06-16 at 8 56 03 am

Is this the expected behavior?

@phinze
Copy link
Contributor

phinze commented Jun 16, 2015

Ah yes - we should detect this as "drift" of the instance_type param. Tagged as a bug and pushing a fix now.

@nwalke
Copy link
Contributor Author

nwalke commented Jun 16, 2015

Awesome @phinze. You guys are closing these bugs so fast!

@CpuID
Copy link
Contributor

CpuID commented Jul 2, 2015

@phinze not sure if this is actually fixed...? Just had it happen in 0.6.0

@CpuID
Copy link
Contributor

CpuID commented Jul 2, 2015

@phinze ignore me, just noticed the .tf file was out of date, so it was trying to make a legitimate change. false alarm.

@ghost
Copy link

ghost commented May 1, 2020

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.

@ghost ghost locked and limited conversation to collaborators May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants