{"action":"created","issue":{"url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/527","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/527/labels{/name}","comments_url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/527/comments","events_url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/527/events","html_url":"https://github.com/spring-cloud/spring-cloud-config/issues/527","id":183628251,"number":527,"title":"Best practices on handling GIT repository inavailability","user":{"login":"pavlo","id":196921,"avatar_url":"https://avatars.githubusercontent.com/u/196921?v=3","gravatar_id":"","url":"https://api.github.com/users/pavlo","html_url":"https://github.com/pavlo","followers_url":"https://api.github.com/users/pavlo/followers","following_url":"https://api.github.com/users/pavlo/following{/other_user}","gists_url":"https://api.github.com/users/pavlo/gists{/gist_id}","starred_url":"https://api.github.com/users/pavlo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pavlo/subscriptions","organizations_url":"https://api.github.com/users/pavlo/orgs","repos_url":"https://api.github.com/users/pavlo/repos","events_url":"https://api.github.com/users/pavlo/events{/privacy}","received_events_url":"https://api.github.com/users/pavlo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-10-18T09:02:07Z","updated_at":"2016-11-07T17:17:32Z","closed_at":null,"body":"Hey guys!\n\nYesterday Bitbucket SSH was down for quite a bit and it caused us issues with the config server and a bunch of staging apps. I'd like to see if there's recommended way to handle such situations. \n### Prerequisites\n1. There's a GIT repo with configuration property files\n2. There's a Config Server deployment that clones the GIT repo and pulls from there up on client's request\n3. There's an app, a client, that, during its startup, obtains configuration properties from the config server\n### Case 1\n\nSay the GIT repository is not accessible for a reason. We launch config server for the first time and it fails to clone the repo. \n\n**This is fine and expectable, no issue here**.\n### Case 2\n\nWe have successfully launched the Config Server in the past so it has the GIT repository cloned. It however fails to start if we restart it because it can not connect to GIT repo.\n\n**Would it be good to let it boot and get the stuff from the repository it had locally cloned in the past?**\n### Case 3\n\nThe Config Server is up and running but at some point Bitbucket SSH goes down. Config Server continues to operate normally. It however fails when a client request comes in because the server can not pull fresh stuff from GIT repository. \n\n**Would it be good to let it serve the client with data it already has in the local repository in this case?**\n\nCan you please elaborate a bit on the the second and third cases? Am I missing something obvious or even misuse the config server?\n\nThanks!  \n"},"comment":{"url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/comments/258899645","html_url":"https://github.com/spring-cloud/spring-cloud-config/issues/527#issuecomment-258899645","issue_url":"https://api.github.com/repos/spring-cloud/spring-cloud-config/issues/527","id":258899645,"user":{"login":"chuhuethao","id":22963243,"avatar_url":"https://avatars.githubusercontent.com/u/22963243?v=3","gravatar_id":"","url":"https://api.github.com/users/chuhuethao","html_url":"https://github.com/chuhuethao","followers_url":"https://api.github.com/users/chuhuethao/followers","following_url":"https://api.github.com/users/chuhuethao/following{/other_user}","gists_url":"https://api.github.com/users/chuhuethao/gists{/gist_id}","starred_url":"https://api.github.com/users/chuhuethao/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chuhuethao/subscriptions","organizations_url":"https://api.github.com/users/chuhuethao/orgs","repos_url":"https://api.github.com/users/chuhuethao/repos","events_url":"https://api.github.com/users/chuhuethao/events{/privacy}","received_events_url":"https://api.github.com/users/chuhuethao/received_events","type":"User","site_admin":false},"created_at":"2016-11-07T17:17:32Z","updated_at":"2016-11-07T17:17:32Z","body":"Thumbs up as I, too, am trying to solve these issues. Looking through open/closed issues it looks like various folks have had these issues as well. This issue #390 has references to other issues that has addressed Case 2 and Case 3 but not specifically. They simply fixed other issues that happens to fix the issue that that person was having. \r\n\r\nIssue #411 seems to have solved this problem for SVN, and similar changes just need to be applied to the Git environment repo. \r\n\r\nHopefully someone can chime in and help out if I am understanding things correctly. "}}
{"actor":{"display_login":"chuhuethao"}}