spring-cloud / spring-cloud/spring-cloud-config
Migrate from Spring Retry to Spring Framework's native retry features
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
Is your feature request related to a problem? Please describe.
In applications using Spring Boot 4/Spring Framework 7, other libraries in the Spring portfolio switched to using the built-in retry features that superseded the old Spring Retry project (Batch, Integration, AMQP, Kafka, Pulsar...). When using Spring Cloud Config Client, it's necessary to add the extra Spring Retry dependency (which is maintenance only).
Describe the solution you'd like
It would be great if Spring Cloud Config could migrate from the deprecated Spring Retry library to Spring Framework's built-in RetryTemplate infrastructure.
Additional context
https://spring.io/blog/2025/09/09/core-spring-resilience-features
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 Spring Retry usage in the Spring Cloud Config Client and reviewing Spring Framework 7's native RetryTemplate infrastructure. The migration is done when Config Client no longer requires the maintenance-only Spring Retry dependency while retaining its existing retry behavior; run the relevant client tests after locating them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, cloud
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100