Skip to content

Conversation

@solonk8
Copy link
Contributor

@solonk8 solonk8 commented Dec 8, 2017

This provides customer more flexibility to alter the routing behavior. Now through the plugin user can decide whether requests should fail or routes to default connector if there's no existing scope/namePrefix found in the routing config. This could be useful in scenarios that intentional failure is needed.

@jc-fireball
Copy link

where is the requirement coming from?

@solonk8 solonk8 force-pushed the add-fallback-control branch from 230ddab to 6eff4d5 Compare December 21, 2017 01:56
@CLAassistant
Copy link

CLAassistant commented Jun 13, 2020

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Qiyao Qin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants