You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you change the instance type of an instance, when you plan you get:
-/+ aws_instance.foo
instance_type: "m4.2xlarge" => "m4.xlarge" (forces new resource)
However this does not need to be so - the instance can be stopped, instance type changed, and instance type restarted. Doing this means more data is safeguarded (as long as ephemeral disks not used).
It would be better to provide stop/start mechanism
The text was updated successfully, but these errors were encountered:
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
locked and limited conversation to collaborators
Apr 16, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform 0.8.7
If you change the instance type of an instance, when you plan you get:
-/+ aws_instance.foo
instance_type: "m4.2xlarge" => "m4.xlarge" (forces new resource)
However this does not need to be so - the instance can be stopped, instance type changed, and instance type restarted. Doing this means more data is safeguarded (as long as ephemeral disks not used).
It would be better to provide stop/start mechanism
The text was updated successfully, but these errors were encountered: