-
Notifications
You must be signed in to change notification settings - Fork 461
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
Chocolatey Package #668
Comments
The Chocolatey Package can be found here: |
We would prefer to maintain documentation only for officially supported install channels. cc @derekbekoe re: ownership |
I totally understand that. Is there anything to stop Chocolatey becoming a supported install channel, in the same way that brew on Mac is supported? |
Currently, there are installers for the most common platforms, including the MSI for Windows, but it's unfeasible for us to support every single installer. It's great to see a community contributed package and we have an issue tracking this: @gep13 Do you have download numbers for installs through chocolatey? Thanks! |
Closing this so that discussion can move over to Azure/azure-cli#3874 - centered on official support for a package type, not docs. |
The downloads stats for that package can be seen on the package page here: https://chocolatey.org/packages/azure-cli Which is not a small number by any means. Does this help influence the decision? Given that a community package already exists, the amount of work required to take it over would be minimal, and definitely something that we could help getting you set up with. |
As you may be aware, a Chocolatey Community Member has created a Chocolatey Package for the Azure CLI. This makes it easy to install it on a Windows machine using:
choco install azure-cli
In the same way that it is recommended to install on say a Mac using:
brew install azure-cli
Would someone in this team be interested in taking ownership of that package to ensure that it is kept up to date with new releases?
Would you accept a PR to add this information to the install section of the docs for Windows?
The text was updated successfully, but these errors were encountered: