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

Simplify CLI installation commands #6896

Open
rm3l opened this issue Jun 15, 2023 · 2 comments
Open

Simplify CLI installation commands #6896

rm3l opened this issue Jun 15, 2023 · 2 comments
Labels
area/Linux Issues or PRs specific to Linux area/MacOS Issues or PRs specific to MacOS area/UX Issues or PRs related to User Experience area/Windows Issues or PRs specific to Windows kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation 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 Jun 15, 2023

/kind feature

DevTools week idea

Which functionality do you think we should add?

Make it easier for developers to download and install odo binaries.

For example, via something like this:

curl -sL https://get.odo.dev | sh # with options to control what to install, like odo version(nightly, latest, or specific version), destination path, ...]

I was thinking of a convenience script that could be downloaded and piped via a single command, but there could be other options of course: integration with package managers...

I am not familiar with Windows, but I guess it should be possible to do something similar. Or the WinGet or Chocolatey packages (#4042) could be helpful as well.

I looked at some already closed issues and found a similar idea discussed (and implemented?)

Why is this needed?

The installation documentation requires running a few manual commands after clicking on the right tab to select the right system architecture and operating system. While this is great for auditing purposes, I think this is a typical example of something that a script could easily determine and perform.

Sure, there are pros and cons when using a one-liner convenience script, such as security implications. So it should still remain possible to run all commands manually if needed, as done currently.

@rm3l rm3l added area/UX Issues or PRs related to User Experience area/MacOS Issues or PRs specific to MacOS area/Windows Issues or PRs specific to Windows area/Linux Issues or PRs specific to Linux labels Jun 15, 2023
@openshift-ci openshift-ci bot added the kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation label Jun 15, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Jun 15, 2023
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 Nov 28, 2023
@rm3l
Copy link
Member Author

rm3l commented Nov 28, 2023

/remove-lifecycle stale
/lifecycle frozen
/priority Low
/remove-status needs-triage

@openshift-ci openshift-ci bot added priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. 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. labels Nov 28, 2023
@rm3l rm3l removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/Linux Issues or PRs specific to Linux area/MacOS Issues or PRs specific to MacOS area/UX Issues or PRs related to User Experience area/Windows Issues or PRs specific to Windows kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation 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

1 participant