{"action":"opened","issue":{"url":"https://api.github.com/repos/flynn/flynn/issues/4009","repository_url":"https://api.github.com/repos/flynn/flynn","labels_url":"https://api.github.com/repos/flynn/flynn/issues/4009/labels{/name}","comments_url":"https://api.github.com/repos/flynn/flynn/issues/4009/comments","events_url":"https://api.github.com/repos/flynn/flynn/issues/4009/events","html_url":"https://github.com/flynn/flynn/issues/4009","id":216840710,"number":4009,"title":"Update cluster by restoring backup without automatic domain-migration","user":{"login":"n0daft","id":2951619,"avatar_url":"https://avatars0.githubusercontent.com/u/2951619?v=3","gravatar_id":"","url":"https://api.github.com/users/n0daft","html_url":"https://github.com/n0daft","followers_url":"https://api.github.com/users/n0daft/followers","following_url":"https://api.github.com/users/n0daft/following{/other_user}","gists_url":"https://api.github.com/users/n0daft/gists{/gist_id}","starred_url":"https://api.github.com/users/n0daft/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/n0daft/subscriptions","organizations_url":"https://api.github.com/users/n0daft/orgs","repos_url":"https://api.github.com/users/n0daft/repos","events_url":"https://api.github.com/users/n0daft/events{/privacy}","received_events_url":"https://api.github.com/users/n0daft/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-03-24T16:37:38Z","updated_at":"2017-03-24T16:37:38Z","closed_at":null,"body":"I noticed that when installing flynn via the web installer and specifying a cluster backup file the installer automatically creates a new domain and migrates from the old to the new.\r\n\r\nCan this behavior be controlled? The old cluster had a custom domain which should stay the way it was. The aim is to update to new flynn versions with the least amount of work and time possible. "}}
{"actor":{"display_login":"n0daft"}}