-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
router: Add name and namespace templates params #9159
router: Add name and namespace templates params #9159
Conversation
Add "Name" and "Namespace" to ServiceAliasConfig, and set them in the template router's AddRoute, in order to make these route parameters available for custom configuration templates.
I created an example template that uses these parameters in order to restrict the use of custom certificates and hosts to routes in specific namespaces. |
openshift-bot, please [test] again! |
LGTM @smarterclayton PTAL This is much less scary! Thanks @Miciah |
lgtm as well [merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/4446/) (Image: devenv-rhel7_4312) |
Evaluated for origin merge up to 85f67f5 |
Flaked again. Please [test] again! |
Evaluated for origin test up to 85f67f5 |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/4446/) |
Add
Name
andNamespace
toServiceAliasConfig
, and set them in the template router'sAddRoute
, in order to make these route parameters available for custom configuration templates.[test]