spring-cloud / spring-cloud/spring-cloud-config
Composite env repo version is always null
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
The response from the config server has fields for label and version, but these are null when using the composite environment repository feature. It would be nice if the response from the config server accommodated the composite repository feature somehow. Unfortunately it might be a breaking change to do so since there would be multiple versions and only currently one version field in the response.
This was mentioned originally in #1007
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 reading issue #1007 and the composite environment repository handling in the config server. Determine how label and version should represent multiple repositories without silently breaking the existing response contract. Done means the response shape and compatibility behavior are clearly specified for implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100