-
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
View, set and unset "Ephemeral" using "odo preference" commands #4327
Comments
@dharmit: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@dharmit: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Well this got addressed already in #4316 /close |
@dharmit: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Which functionality do you think we should add?
PR #4316 adds feature to ensure that odo uses a PVC by default for storing the source code on remote k8s/ocp cluster. The way this happens is by referring the value of
Ephemeral
in odo's preference file (~/.odo/preference.yaml
).However, odo doesn't correctly view, set or unset this setting in the preference file.
Why is this needed?
This is needed so that users can view, set and unset the value of "Ephemeral" in odo preferences.
/kind bug (since it should have ideally been added as a part of #4316)
/kind feature (since it's still something new that doesn't exist in odo code)
/area config (since we don't have "preference" label)
/good-first-issue
The text was updated successfully, but these errors were encountered: