{"action":"opened","issue":{"url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/514","repository_url":"https://api.github.com/repos/spring-cloud/spring-cloud-config","labels_url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/514/labels{/name}","comments_url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/514/comments","events_url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/514/events","html_url":"https://github.com/spring-cloud/spring-cloud-config/issues/514","id":179258623,"number":514,"title":"discovery data for config server never updates after startup","user":{"login":"whboyd","id":10451356,"avatar_url":"https://avatars.githubusercontent.com/u/10451356?v=3","gravatar_id":"","url":"https://api.github.com/users/whboyd","html_url":"https://github.com/whboyd","followers_url":"https://api.github.com/users/whboyd/followers","following_url":"https://api.github.com/users/whboyd/following{/other_user}","gists_url":"https://api.github.com/users/whboyd/gists{/gist_id}","starred_url":"https://api.github.com/users/whboyd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/whboyd/subscriptions","organizations_url":"https://api.github.com/users/whboyd/orgs","repos_url":"https://api.github.com/users/whboyd/repos","events_url":"https://api.github.com/users/whboyd/events{/privacy}","received_events_url":"https://api.github.com/users/whboyd/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-26T15:20:19Z","updated_at":"2016-09-26T15:20:19Z","closed_at":null,"body":"It appears that in discovery-first mode, the config client is not updating its location information for the config server when that data changes in eureka (i.e. when a config server instance is removed or added in eureka). Is this currently expected behavior, or am I doing something wrong?\r\n\r\n```\r\nspring:\r\n    cloud:\r\n        config:\r\n            enabled: true\r\n            failFast: true\r\n            discovery:\r\n                enabled: true\r\neureka:\r\n    client:\r\n        serviceUrl:\r\n            defaultZone: [[my eureka defaultZone]]\r\n```\r\n\r\nWhen I take down the first config server instance, the configserver healthcheck in the app begins to fail despite there being a separate working node. The same occurs if I restart the config server node with a new password in the eureka metadataMap, in which case the client keeps trying to use the old password."}}
{"actor":{"display_login":"whboyd"}}