spring-cloud / spring-cloud/spring-cloud-gateway
Versioning of Custom Filters
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
Please share if there an inbuilt way to run multiple versions of a custom filter allowing a gradual upgrade path.
For Example:
If a filter, say, CustomFilter is being used by several routes requires a change that could have a large impact, we would prefer a gradual upgrade process with only selective routes going first. Of-course, we can make multiple copies of the filter, like CustomFilterV1, CustomFilterV2 etc. but that leads to a maintenance overhead.
Is there anything inbuilt to make it easier.
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
The issue names no files, tests, or concrete entry point. Start by reviewing Spring Cloud Gateway’s custom-filter and route-configuration extension points, then determine whether version selection can be specified per route; done means documenting an existing mechanism or defining the required compatibility behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100