title: How do I setup a local fallback config for Spring Cloud Config service incase remote repo is not available?
body: <p>We are planning to utilize Spring Cloud Config for our service. Our biggest concern is that when the container starts up, it relies on github to be available all the time so that it can pull the config files. In case github is down, what is the best practice to mitigate the issue? </p>
  
  <p>I was thinking of storing a local folder of the configs as a backup and configuring the application.yml to fallback to it (I do not know how).</p>
  
  <p>I was going to use a Composite Environment Repositories
  Please see here: <a href="https://cloud.spring.io/spring-cloud-config/multi/multi__spring_cloud_config_server.html" rel="nofollow noreferrer">Section 2.1.8</a></p>
  
  <p>However it states:</p>
  
  <blockquote>
    <p>Any type of failure when retrieving values from an environment repository results in a failure for the entire composite environment.</p>
  </blockquote>
  
  <p>This means if the git retrieve fails, it does not fall back to the local component of the composite. I wish it did. Have any of you handled a similar problem? How did you solve it?</p>
  
  <p>Here is a good article about best practices. However, I need a workaround for case 1: <a href="https://github.com/spring-cloud/spring-cloud-config/issues/527" rel="nofollow noreferrer">Best practices on handling GIT repository inavailability</a></p>