/actuator/health/configServer indicator not useful since it uses local git cache

The /actuator/health/configServer endpoint always returns UP so long as the local git cache contains a repo for the application used for the health check. This would be okay if the ConfigServer serves only one client app.

However, when it serves multiple clients, it's not helpful. So, if it has local git cache for the health-indicator app, then it always returns UP even when git server is down. But if a different app is requested and git server is down, that other app will receive a 404. Yet the config server reports as UP, so load balancers won't take it out of the pool. (On the other hand, taking it out of the pool would cause clients to try the next URL if they are configured with multiple URLs.)

Can this health indicator be updated to report the health without relying on local git cache? To keep current behavior, perhaps make it configurable whether or not it uses local git cache during health check?

Start at the /actuator/health/configServer entry point and trace how the health check uses the local git cache. Define and verify behavior when multiple clients are served and the git server is unavailable; done means the reported health accurately reflects that situation while any retained local-cache behavior is configurable.