-
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
Fix the documentation to show how to set a custom message #11117
Fix the documentation to show how to set a custom message #11117
Conversation
{ "name": "RESPONSE", | ||
"value": "Hello World!" | ||
} | ||
], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would look nicer if you closed out the containers block.
I had added a feature to get a custom message from hello-openshift by using an environment variable. But when I documented it, I used oc set env (which worked for me since I was using a dc to test, but with a bare pod, it can not work). So, this changes the documentation to show how to set an env in the pod definition, and how to make use of it. Fixes openshift#11093
bbc673b
to
9d9dc6d
Compare
lgtm [merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/9398/) (Image: devenv-rhel7_5093) |
Evaluated for origin merge up to 9d9dc6d |
[Test]ing while waiting on the merge queue |
Evaluated for origin test up to 9d9dc6d |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/9398/) |
I had added a feature to get a custom message from hello-openshift by
using an environment variable. But when I documented it, I used oc
set env (which worked for me since I was using a dc to test, but with
a bare pod, it can not work). So, this changes the documentation to
show how to set an env in the pod definition, and how to make use of
it.
Fixes #11093