spring-cloud / spring-cloud/spring-cloud-gateway
Enable to merge defined predicates/filters with default ones while using Discovery client route locator
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
Describe the solution you'd like
I would simply like to have a new boolean property, such as spring.cloud.gateway.discovery.locator.with-default-predicates-filters, enabling not having to redefine the defaults predicate(s) and filter(s) when I simply need to append such a new predicate or filter. This would largely simplify users' configuration.
Describe alternatives you've considered
The only alternative today is to follow what is mentioned in the documentation, that is not to forget to copy/paste the default configuration (path predicate and rewrite path filter as defined in GatewayDiscoveryClientAutoConfiguration).
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 GatewayDiscoveryClientAutoConfiguration and the documentation describing the default path predicate and rewrite path filter. Trace how Discovery client route locator configuration currently replaces those defaults, then define the requested boolean property's expected merge behavior. Done means users can append predicates or filters without copying the documented defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100