New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[policy] Dynamic routing policy #87

Closed
AnselmeDewavrin opened this Issue Jun 21, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@AnselmeDewavrin

AnselmeDewavrin commented Jun 21, 2016

Dear all,

An idea : it be great to have a dynamic routing policy based on this scheme:
regex1 match -> url1 with dynamic content
regex2 match -> url2 with dynamic content
...
With dynamic content made of properties, dsl, etc.
Thanks,
Anselme

@brasseld

This comment has been minimized.

Member

brasseld commented Jun 21, 2016

Hi @AnselmeDewavrin,

So the idea would be to create a new policy for dynamic-routing.
This policy expects some rules in its configuration and a rule should be:
If Regex 1 match then redirect to an URL 1
If Regex 2 match then redirect to an URL 2

Defined URLs must themselves be dynamic by using Expression Language and Regex capture / replacement.

@brasseld brasseld changed the title from dynamic routing policy to [policy] Dynamic routing policy Jun 21, 2016

@brasseld

This comment has been minimized.

Member

brasseld commented Jun 21, 2016

Hi @AnselmeDewavrin,

There is now a new policy named "Dynamic Routing" which allows this kind of dynamic endpoint addressing.

https://github.com/gravitee-io/gravitee-policy-dynamic-routing

This policy will be available as part of release 0.14.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment