{"action":"created","issue":{"url":"https://api.github.com/repos/vfarcic/docker-flow-proxy/issues/23","repository_url":"https://api.github.com/repos/vfarcic/docker-flow-proxy","labels_url":"https://api.github.com/repos/vfarcic/docker-flow-proxy/issues/23/labels{/name}","comments_url":"https://api.github.com/repos/vfarcic/docker-flow-proxy/issues/23/comments","events_url":"https://api.github.com/repos/vfarcic/docker-flow-proxy/issues/23/events","html_url":"https://github.com/vfarcic/docker-flow-proxy/issues/23","id":157838682,"number":23,"title":"Proxy doesn't react to changed IP and/or port for service in Consul","user":{"login":"wilkko","id":952106,"avatar_url":"https://avatars.githubusercontent.com/u/952106?v=3","gravatar_id":"","url":"https://api.github.com/users/wilkko","html_url":"https://github.com/wilkko","followers_url":"https://api.github.com/users/wilkko/followers","following_url":"https://api.github.com/users/wilkko/following{/other_user}","gists_url":"https://api.github.com/users/wilkko/gists{/gist_id}","starred_url":"https://api.github.com/users/wilkko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wilkko/subscriptions","organizations_url":"https://api.github.com/users/wilkko/orgs","repos_url":"https://api.github.com/users/wilkko/repos","events_url":"https://api.github.com/users/wilkko/events{/privacy}","received_events_url":"https://api.github.com/users/wilkko/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":17,"created_at":"2016-06-01T07:13:49Z","updated_at":"2016-08-04T13:28:02Z","closed_at":null,"body":"How to handle when information changes in Consul? I've seen that for example when you restart a container from Shipyard UI port might change and proxy is not able to follow and reconfigure proxy is required.\r\n\r\nNormally I would run Consul template in daemon mode to solve this but don't know how Docker-flow-proxy is internally supposed to work."},"comment":{"url":"https://api.github.com/repos/vfarcic/docker-flow-proxy/issues/comments/237552389","html_url":"https://github.com/vfarcic/docker-flow-proxy/issues/23#issuecomment-237552389","issue_url":"https://api.github.com/repos/vfarcic/docker-flow-proxy/issues/23","id":237552389,"user":{"login":"vfarcic","id":5716227,"avatar_url":"https://avatars.githubusercontent.com/u/5716227?v=3","gravatar_id":"","url":"https://api.github.com/users/vfarcic","html_url":"https://github.com/vfarcic","followers_url":"https://api.github.com/users/vfarcic/followers","following_url":"https://api.github.com/users/vfarcic/following{/other_user}","gists_url":"https://api.github.com/users/vfarcic/gists{/gist_id}","starred_url":"https://api.github.com/users/vfarcic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vfarcic/subscriptions","organizations_url":"https://api.github.com/users/vfarcic/orgs","repos_url":"https://api.github.com/users/vfarcic/repos","events_url":"https://api.github.com/users/vfarcic/events{/privacy}","received_events_url":"https://api.github.com/users/vfarcic/received_events","type":"User","site_admin":false},"created_at":"2016-08-04T13:28:02Z","updated_at":"2016-08-04T13:28:02Z","body":"If you're in AWS, you might want to try \"Docker for AWS\". Please note that it's still in beta.\r\n\r\nPersonally, when using cloud providers, I use Packer to create images (AMIs), Ansible to provision them, and Terraform to instantiate. Since some information is not available when creating AMIs, Terraform usually does initializations as well. In case of the new Swarm, Packer/Ansible create AMI with Docker and whatever else is needed, and Terraform creates as many instances as I need. When an instance is created, Terraform also runs \"docker swarm init\" or \"docker swarm join\". In such a combination, idempotency is not important since I don't try to maintain servers in the \"correct\" state. I usually kill them and create new ones whenever I need something."}}
{"actor":{"display_login":"vfarcic"}}