Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add docs for Config Server behavior when backend is not accessible #572

Open
csterwa opened this issue Nov 30, 2016 · 0 comments
Open

Add docs for Config Server behavior when backend is not accessible #572

csterwa opened this issue Nov 30, 2016 · 0 comments

Comments

@csterwa
Copy link

csterwa commented Nov 30, 2016

The current Spring Cloud Config docs describe different configuration parameters for setting up a backend such as a Git repo. It would be helpful to describe expected behavior at runtime when the backend that was setup is not accessible for any number of reasons (network, crash, misconfiguration). Some of the situations to describe could be:

  • What happens when Config Server starts up but is not able to access backend (Git)?
  • What happens when backend is not accessible after Config Server already started successfully and pulled configuration values?
  • What happens if backend becomes unavailable during process of pulling configuration values?
  • How is refresh affected by backend becoming unaccessible?

I'm sure that there are other situations to be described. Please let me know if there are any questions. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants