spring-cloud / spring-cloud/spring-cloud-commons
Clearly document the order of various PropertySource in Spring Cloud
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 751
- Forks
- 744
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 9
Description
Unlike Spring Boot, which clearly states the order of various PropertySource, Spring Cloud chooses to be vague. A non-exhaustive list contains application.yml, and bootstrap.yml and their profile-specific versions, config service application.yml and service specific files and their profile-specific versions, and perhaps Kubernetes PropertySource. Can it get more confusing if not documented?
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 the linked Spring Boot external configuration reference, then inventory the listed application.yml, bootstrap.yml, config service files, profile-specific files, and Kubernetes PropertySource. Done means the Spring Cloud property-source precedence is clearly documented, including the relevant profile and service-specific variants.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100