spring-cloud / spring-cloud/spring-cloud-commons
External property file change watch
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 751
- Forks
- 744
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 9
Description
Original https://github.com/spring-cloud/spring-cloud-kubernetes/issues/190
Code should live here since it is not specific to spring cloud.
See jhipster CloudConfigRefreshService for example.
Useful for spring cloud k8s.
Related #604
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 original issue and the jhipster CloudConfigRefreshService example at src/main/java/io/github/jhipster/registry/service/CloudConfigRefreshService.java. Compare that approach with the related #604 context and determine the expected external property-file watch behavior. Done means the shared Spring Cloud code supports the intended refresh use case for Spring Cloud Kubernetes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kubernetes, spring-boot
- Domain
- backend, cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100