-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Feature Request: introduces a "setup" mode to download the CLI (latest or specified version) instead of using docker image #76
Comments
I created a new branch "v2" that switch from a Docker Github action to a Javascript Github Action.
You can see what changed by looking at: https://github.com/updatecli/updatecli-action/compare/main..v2?expand=1 Please note that the content of the directory |
If we really want to use the docker github action then I would just keep maintaining the branch v1 |
I now realize that I didn't follow this interface but instead went with
I am open to feedback but I think @dduportal suggestion is better as it makes it more obvious that the binary is available on the runner and that we are not using a docker container |
I am now wondering if I shouldn't just take care of downloading the binary and stick to
|
absolutely! That is the intent of my initial proposal, to focus on the important part: "getting updatecli with the correct version (CPU arch + OS) installed in the PATH" |
Right final version before a v2.0.0 |
Ready to be used |
Is your feature request related to a problem?
The actual action which uses the updatecli Docker images is not really convenient to use:
Solution you'd like
A "setup" mode would solve all this problems, a bit like other actions such as https://github.com/Azure/setup-helm or https://github.com/actions/setup-java.
Alternatives you've considered
curl -sSLO && chmod a+x
in pur shellAnything else?
No response
The text was updated successfully, but these errors were encountered: