-
Notifications
You must be signed in to change notification settings - Fork 244
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
Should we allow/prevent user to set DebugPort as environment variable? #2183
Comments
Not sure how we could check this. |
We have a separate module on setting / unsetting variables now which users can refer to: openshift/openshift-docs#18478 |
@dharmit a separate module on setting / unsetting variables is documented by Yana here: https://docs.openshift.com/container-platform/4.2/cli_reference/openshift_developer_cli/managing-environment-variables-in-odo.html Also it will be covered as part of this issue: #2227 |
In it's current state, the link you mentioned talks about environment variables in general. We're discussing a particular environment variable ( |
@dharmit documentation on the debug feature was covered through this PR: openshift/openshift-docs#19750 can you confirm if we can close this issue, please? |
Looks good to me. Thanks for addressing this @boczkowska & @Preeticp ! |
[kind/bug]
What versions of software are you using?
odo version
: masterHow did you run odo exactly?
I set the DebugPort using environment variable approach (
odo config set --env
) but tried to unset it using normal approach (odo config unset DebugPort
) and was left confused why it's not getting unset.odo config set -e DebugPort 9090
odo config unset DebugPort
Actual behavior
Not really a bug but as a user I was wondering if this is a bug.
Expected behavior
TBD
Any logs, error output, etc?
In this case, it was my mistake to set DebugPort as env var and then unset it using
odo config unset
. Should we have a check or documentation or anything to prevent user from doing this or should this be just passed as user error?It seems more like user error to me than anything that tool should be worried about.
The text was updated successfully, but these errors were encountered: