Possibility to enhance cloneOnStart to not delete directory

Hello,

We're using cloud config server with a git backend and our current setup of bitbucket cluster doesn't make it to be considered HA (because it is not clustered across multiple datacenters). So I would like to support a failover mode in cloud config.

I would ideally like to use the "cloneOnStart" feature, but since it deletes and recreates the base directory - it would mean that a config server has a hard dependency on bitbucket to even start the server. How can I enhance it to not delete the base directory and rather do a hard reset on start up, so the previous state of all my git repos will keep the application functioning?

The current implementation of the environment repository makes it very tough to enhance it due to most of the logic being in private methods.

Please advice.

Thanks!

Start with the environment repository and the cloneOnStart implementation, focusing on how the base directory is deleted and recreated for a Git backend. Review the private-method-heavy logic and determine how startup could preserve existing repositories while resetting them. Done means the server can start from the previous repository state when the Bitbucket backend is unavailable.