{"action":"closed","issue":{"url":"https://api.github.com/repos/terraform-providers/terraform-provider-digitalocean/issues/147","repository_url":"https://api.github.com/repos/terraform-providers/terraform-provider-digitalocean","labels_url":"https://api.github.com/repos/terraform-providers/terraform-provider-digitalocean/issues/147/labels{/name}","comments_url":"https://api.github.com/repos/terraform-providers/terraform-provider-digitalocean/issues/147/comments","events_url":"https://api.github.com/repos/terraform-providers/terraform-provider-digitalocean/issues/147/events","html_url":"https://github.com/terraform-providers/terraform-provider-digitalocean/issues/147","id":366742368,"node_id":"MDU6SXNzdWUzNjY3NDIzNjg=","number":147,"title":"Floating IP assignment is lost when performing blue/green deployment","user":{"login":"dave-lew99","id":547612,"node_id":"MDQ6VXNlcjU0NzYxMg==","avatar_url":"https://avatars1.githubusercontent.com/u/547612?v=4","gravatar_id":"","url":"https://api.github.com/users/dave-lew99","html_url":"https://github.com/dave-lew99","followers_url":"https://api.github.com/users/dave-lew99/followers","following_url":"https://api.github.com/users/dave-lew99/following{/other_user}","gists_url":"https://api.github.com/users/dave-lew99/gists{/gist_id}","starred_url":"https://api.github.com/users/dave-lew99/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dave-lew99/subscriptions","organizations_url":"https://api.github.com/users/dave-lew99/orgs","repos_url":"https://api.github.com/users/dave-lew99/repos","events_url":"https://api.github.com/users/dave-lew99/events{/privacy}","received_events_url":"https://api.github.com/users/dave-lew99/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-04T11:21:52Z","updated_at":"2018-10-04T18:47:56Z","closed_at":"2018-10-04T18:47:56Z","author_association":"NONE","body":"Hi there,\r\n\r\n### Terraform Version\r\nTerraform v0.11.8\r\n\r\n### Affected Resource(s)\r\nPlease list the resources as a list, for example:\r\n- digitalocean_droplet\r\n- digitalocean_floating_ip_assignment\r\n\r\nIf this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.\r\n\r\n### Terraform Configuration Files\r\n```hcl\r\nresource \"digitalocean_droplet\" \"test-1\" {\r\n    image = \"centos-7-x64\"\r\n    name = \"test-1\"\r\n    region = \"fra1\"\r\n    size = \"s-1vcpu-1gb\"\r\n    private_networking = false\r\n    lifecycle {\r\n        create_before_destroy = true\r\n    }\r\n}\r\n\r\nresource \"digitalocean_floating_ip\" \"testip\" {\r\n  region     = \"fra1\"\r\n\r\n}\r\nresource \"digitalocean_floating_ip_assignment\" \"testip-assignment\" {\r\n  ip_address = \"${digitalocean_floating_ip.testip.id}\"\r\n  droplet_id = \"${digitalocean_droplet.test-1.id}\"\r\n    lifecycle {\r\n        create_before_destroy = true\r\n    }\r\n}\r\n```\r\n\r\n### Debug Output\r\n\r\n\r\n### Panic Output\r\nIf Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the `crash.log`.\r\n\r\n### Expected Behavior\r\nWhen updating a droplet with a new image, the new droplet should be provisioned then the floating IP assignment is changed over to the new droplet, before destroying the old droplet.\r\n\r\n### Actual Behavior\r\nThe floating IP assignment briefly swaps to the newly provisioned instance before being destroyed entirely. Running `terraform apply` again fixes the association.\r\n\r\n### Steps to Reproduce\r\nPlease list the steps required to reproduce the issue, for example:\r\n1. `terraform apply`\r\n2. Change the `image` value\r\n3. Run `terraform apply`\r\n\r\n\r\n### References\r\nAre there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:\r\n- Maybe GH-99\r\n"}}
{"actor":{"display_login":"andrewsomething"}}