spring-cloud / spring-cloud/spring-cloud-config
Use of Config server/Credhub with a client with the propertie spring.cloud.config.name with multi names
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
Describe the bug
In the client app i have the configuration:
spring.cloud.config.name=nomapp,application,nom2
The problem is that the config server want to load the file (see in actuator/env of the app):
{"name":"bootstrapProperties-credhub-nomapp,application,nom2-cloud-master","properties":{}}
But it's not possible to add in Credhub a secret with a path separated with commas.
If i try with "spring.cloud.config.name=nomapp" it worked.
Is it possible to do that? Or is it a futur feature?
Thank you
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the client configuration with spring.cloud.config.name set to "nomapp,application,nom2" and inspect the actuator/env entry for the generated Credhub path. Trace how the config server handles the comma-separated names and compare it with the working single-name case. Done means the configured names can be resolved through Credhub without requiring a comma-containing secret path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100