spring-cloud / spring-cloud/spring-cloud-config
Optimization: only use remote properties if application name or profiles change
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
In a context hierarchy there's no sense in all contexts loading the same properties (and the parent will always have the remote values since it has to be initialized before a child is added).
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 how context hierarchies load remote properties and how application names or profiles are compared between parent and child contexts. The change is done when child contexts avoid reloading identical remote properties while still loading them when the application name or profiles change; no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100