Is your feature request related to a problem? Please describe.
When the spring.cloud.config.server.bootstrap property is set to true, the config-server should configure itself like it was any other config-client, which it does well, as long as you don't need a resource, like a logback-spring.xml during bootstraping.
This is not a problem for clients, because I can just use a config like this: logging.config=${spring.cloud.config.uri:http://localhost:8888/}/${spring.application.name}/${spring.profiles.active:default}/master/logback-spring.xml and the client will send another request to the config server asking for this resource.
The problem is that during config-server bootstraping, this endpoint is not yet available.
Describe the solution you'd like
I don't know if there are other usecases (not logging reinitialization related) where this issue arises. If there aren't (which I suspect is the case) than the solution is simply to try and request the resource bypassing the endpoint, for example by invoking this.repository.findOne(name, profiles, label, includeOrigin); directly.
code taken from org.springframework.cloud.config.server.environment.EnvironmentController:136
If there are other usecases, we might need a more sophisticated solution.
Describe alternatives you've considered I have considered some hacky solutions by defining root search locations, but these are shady and situational.
Comment From: spencergibb
After discussion with the team, we've decided the premise is good. We would need something general that works in many cases. It might require some design on our side first.