spring-cloud / spring-cloud/spring-cloud-config
Add API To Config Server To Return Configuration Only For Profiles
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
Spring Boots Config Data support separates loading config data into two steps, configuration data without profiles and then configuration with profiles. We try our best to label PropertySources as PROFILE_SPECIFIC in ConfigServerConfigDataLoader but its error prone because depending on the configuration of the config server the profile separator could be anything. AWS Secrets Manage, AWS Parameter Store and Vault all allow for profile separator configuration.
We know when the config data API is only requesting profile specific property sources so we could make a specific request to the config server to just return the profile specific property sources.
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 with ConfigServerConfigDataLoader and trace how the config data API requests and labels property sources for profile-specific data. Identify the config-server endpoint and client changes needed to request only profile-specific property sources, then verify that profile-separated sources are no longer inferred from separators.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend-api-design, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100