spring-cloud / spring-cloud/spring-cloud-config
Add profile to config server response data
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
Currently, the response from config server contains the profiles used to make the call.
{
"name": "foo",
"profiles": [
"development"
]
...
As part of ongoing ConfigData changes, it's useful to know the specific profile associated with the property source if applicable. See #1795. This matches profile against the name, but if available in the response, no string matching would be needed.
See https://github.com/spring-projects/spring-boot/issues/25940#issuecomment-820647528
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 tracing where the config server response and its property sources are assembled, using the ongoing ConfigData changes in #1795 and the referenced Spring Boot discussion as context. Done means the response identifies the specific profile associated with each applicable property source without requiring name matching.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100