{"action":"opened","issue":{"url":"https://api.github.com/repos/manheim/cf_deployer/issues/45","repository_url":"https://api.github.com/repos/manheim/cf_deployer","labels_url":"https://api.github.com/repos/manheim/cf_deployer/issues/45/labels{/name}","comments_url":"https://api.github.com/repos/manheim/cf_deployer/issues/45/comments","events_url":"https://api.github.com/repos/manheim/cf_deployer/issues/45/events","html_url":"https://github.com/manheim/cf_deployer/issues/45","id":164929978,"number":45,"title":"Add default timeout on deployment, in case stack gets stuck in UPDATE_IN_PROGRESS permanently","user":{"login":"kmanning","id":1686022,"avatar_url":"https://avatars.githubusercontent.com/u/1686022?v=3","gravatar_id":"","url":"https://api.github.com/users/kmanning","html_url":"https://github.com/kmanning","followers_url":"https://api.github.com/users/kmanning/followers","following_url":"https://api.github.com/users/kmanning/following{/other_user}","gists_url":"https://api.github.com/users/kmanning/gists{/gist_id}","starred_url":"https://api.github.com/users/kmanning/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kmanning/subscriptions","organizations_url":"https://api.github.com/users/kmanning/orgs","repos_url":"https://api.github.com/users/kmanning/repos","events_url":"https://api.github.com/users/kmanning/events{/privacy}","received_events_url":"https://api.github.com/users/kmanning/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/manheim/cf_deployer/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-11T20:43:58Z","updated_at":"2016-07-11T20:43:58Z","closed_at":null,"body":"We've seen issues in AWS, where a stack can get caught in UPDATE_IN_PROGRESS permanently.  During a deployment, we poll the status for the stack, and wait until it either has a success, or a failure status - if the stack is perpetually in neither of those states, the polling (and therefore the deployment) will continue forever.  \r\n\r\nAdd a default/configurable timeout around checking the stack status, so that such problems can be detected in an automated pipeline.\r\n\r\nhttps://github.com/manheim/cf_deployer/blob/master/lib/cf_deployer/stack.rb#L156\r\n\r\nNoted by @ryanrwalker during code review for Issue #38."}}
{"actor":{"display_login":"kmanning"}}