spring-cloud / spring-cloud/spring-cloud-config
NativeEnvironmentRepository loads property sources in the wrong order
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
http://localhost:8888/account-service,security-service,generic-service/stg
spring.cloud.config.server.native.searchLocations=classpath:/configs/{application}
results in
"name": "classpath:/configs/generic-service/generic-service-stg.properties",
"name": "classpath:/configs/security-service/security-service-stg.yml",
"name": "classpath:/configs/account-service/account-service-stg.properties",
"name": "classpath:/configs/generic-service/generic-service.properties",
"name": "classpath:/configs/account-service/account-service.properties",
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 NativeEnvironmentRepository and reproduce the request using the listed application order and spring.cloud.config.server.native.searchLocations value. Compare the returned property-source order with the requested account-service, security-service, generic-service sequence; done means the response preserves the intended order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100