Local Standby if Remote Repository is not available

This issue has been addressed here How do I setup a local fallback config for Spring Cloud Config service incase remote repo is not available? . However the solution seems to be very manual.

I would have hoped that by using order I could;
order:1 try git and if it is accessible, clone/pull to baseDir. If GIT access fails use
order:2 native to access git:baseDir via native:seachLocations.

I would have thought, it would be better for order:1 to not delete baseDir before attempting GIT and only if GIT is available proceed with re-building baseDir.

As the linked solution suggests, in order to get around this problem, I need to start config with 'clone/pull' set, then remove, before the next run.

I see this issue mentioned in a number of places e.g. [#631] (https://github.com/spring-cloud/spring-cloud-config/issues/631) - however this issue and others seems to all point to each other and I don't see a resolution.

Read the linked Stack Overflow solution and related issue #631 first, then trace the existing git clone/pull and native search-location behavior. Done means a failed remote repository access preserves and uses the local fallback without requiring the manual startup sequence described here.