Skip to content
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

User Preference to set value for platform #6331

Open
Tracked by #6991
rm3l opened this issue Nov 22, 2022 · 3 comments
Open
Tracked by #6991

User Preference to set value for platform #6331

rm3l opened this issue Nov 22, 2022 · 3 comments
Labels
area/odo-on-podman Issues or PRs related to running odo against Podman lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.

Comments

@rm3l
Copy link
Member

rm3l commented Nov 22, 2022

Exposing as part of the --run-on --platform flag is useful if someone wants to switch between the two modes. Have we considered also putting it as part of the preference so that the user doesn't have to specify that on every odo dev or odo deploy command?

Originally posted by @elsony in #6151 (comment)

@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Nov 22, 2022
@rm3l rm3l changed the title Set run-on as User Preference User Preference to set value for run-on Nov 22, 2022
@rm3l
Copy link
Member Author

rm3l commented Nov 22, 2022

Response: #6151 (comment)

Exposing as part of the --run-on flag is useful if someone wants to switch between the two modes. Have we considered also putting it as part of the preference so that the user doesn't have to specify that on every odo dev or odo deploy command?

That makes sense. We can add this. But it is something that we should consider only after we have a more solid implementation and it is ready to be moved out of experimental mode.

@valaparthvi valaparthvi added the priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. label Dec 1, 2022
@valaparthvi
Copy link
Member

I have set a low priority since this should be implemented after odo is more stable on podman.

But it is something that we should consider only after we have a more solid implementation and it is ready to be moved out of experimental mode. #6151 (comment)

@rm3l rm3l added the area/odo-on-podman Issues or PRs related to running odo against Podman label Jan 3, 2023
@rm3l rm3l changed the title User Preference to set value for run-on User Preference to set value for platform Feb 8, 2023
@github-actions
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 17, 2023
@rm3l rm3l added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. labels Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/odo-on-podman Issues or PRs related to running odo against Podman lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
Projects
Status: No status
Development

No branches or pull requests

2 participants