spring-cloud / spring-cloud/spring-cloud-config
Auto refresh properties one node at a time
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
Current Scenario:
- Remote Repository is configured with /monitor git webhook and config server is listening to events to auto refresh config changes.
- All nodes are connected to Spring Cloud Bus and are listening for the refresh event published by the Spring Cloud Config Server.
- Whenever changes are committed to repository, they are reflected to respective nodes.
Problem:
If multiple nodes are running for an app, is it possible to update changes to nodes one at a time?
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 reviewing the described /monitor git webhook flow, Spring Cloud Config Server refresh events, and Spring Cloud Bus propagation to connected nodes. Clarify the required ordering and coordination semantics for updating multiple nodes one at a time; done means changes are applied sequentially rather than simultaneously across nodes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java, spring
- Domain
- backend, cloud, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100