{"action":"created","issue":{"url":"https://api.github.com/repos/hashicorp/terraform/issues/1887","labels_url":"https://api.github.com/repos/hashicorp/terraform/issues/1887/labels{/name}","comments_url":"https://api.github.com/repos/hashicorp/terraform/issues/1887/comments","events_url":"https://api.github.com/repos/hashicorp/terraform/issues/1887/events","html_url":"https://github.com/hashicorp/terraform/issues/1887","id":74834922,"number":1887,"title":"Feature Request: Stop, don't destroy instance on user-data update","user":{"login":"jwaldrip","id":43164,"avatar_url":"https://avatars.githubusercontent.com/u/43164?v=3","gravatar_id":"","url":"https://api.github.com/users/jwaldrip","html_url":"https://github.com/jwaldrip","followers_url":"https://api.github.com/users/jwaldrip/followers","following_url":"https://api.github.com/users/jwaldrip/following{/other_user}","gists_url":"https://api.github.com/users/jwaldrip/gists{/gist_id}","starred_url":"https://api.github.com/users/jwaldrip/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jwaldrip/subscriptions","organizations_url":"https://api.github.com/users/jwaldrip/orgs","repos_url":"https://api.github.com/users/jwaldrip/repos","events_url":"https://api.github.com/users/jwaldrip/events{/privacy}","received_events_url":"https://api.github.com/users/jwaldrip/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-05-10T05:09:11Z","updated_at":"2015-05-12T01:46:12Z","closed_at":null,"body":"when updating user-data, its not required to destroy the instance. In fact, this can be devastating to a etcd cluster. What would be acceptable is for the machines to be stopped, userdata updated, and then started."},"comment":{"url":"https://api.github.com/repos/hashicorp/terraform/issues/comments/101095776","html_url":"https://github.com/hashicorp/terraform/issues/1887#issuecomment-101095776","issue_url":"https://api.github.com/repos/hashicorp/terraform/issues/1887","id":101095776,"user":{"login":"sparkprime","id":168158,"avatar_url":"https://avatars.githubusercontent.com/u/168158?v=3","gravatar_id":"","url":"https://api.github.com/users/sparkprime","html_url":"https://github.com/sparkprime","followers_url":"https://api.github.com/users/sparkprime/followers","following_url":"https://api.github.com/users/sparkprime/following{/other_user}","gists_url":"https://api.github.com/users/sparkprime/gists{/gist_id}","starred_url":"https://api.github.com/users/sparkprime/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sparkprime/subscriptions","organizations_url":"https://api.github.com/users/sparkprime/orgs","repos_url":"https://api.github.com/users/sparkprime/repos","events_url":"https://api.github.com/users/sparkprime/events{/privacy}","received_events_url":"https://api.github.com/users/sparkprime/received_events","type":"User","site_admin":false},"created_at":"2015-05-12T01:46:12Z","updated_at":"2015-05-12T01:46:12Z","body":"So this particular issue is not a problem with GCE as you can update metadata without forceNew.  However there is a similar problem if you want to change zone / scopes without losing the data on your disk.\r\n\r\nThe way I go about doing this is to use a separate disk resource in any situation where the content of the disk is precious in some way.  E.g. obviously for databases this is true, but typically in a node of a load balanced cluster the disk is expendable.  Having a separate disk allows Terraform to recreate the instance without losing the disk (as the disk is not recreated).  I believe this is equivalent to a reboot cycle."}}