search

Azure / azure-cli

Azure Command-Line Interface
MIT License
3.91k stars 2.88k forks source link

Provide `.pkg` installer for macOS #8654

Open marstr opened 5 years ago

marstr commented 5 years ago

Today, we require that macOS users install the Azure CLI using brew or taking their chances and installing via the catch-all bash script.

Forcing folks to use brew feels pretty intrusive. Worse yet, if they only use brew for the azure-cli and have Python previously installed, the brew installed python must override the other version or the azure-cli will fail to load some commands.

In regards to the catch-all script, I think it should be reserved for platforms that are less-mainstream than macOS developers.

We've had some asks for this in the past (#7361), but after diagnosing a few failed installs where the root was folks getting bitten by having a mixed brew/system python environment, it's worth another look.

fishd72 commented 5 years ago

This would be especially helpful for environments where the local user does not have full local admin rights and clients require software to be installed via management tooling.

yonzhan commented 4 years ago

@fengzhou-msft please take a look

breiter commented 4 years ago

My company is standardized on MacPorts for years. We evaluated Homebrew but it is not for us. We considered Joyent's pkgsrc but it wasn't really better than MacPorts for us. Not everyone uses Homebrew and brew certainly is not the official package manager for macOS.

It feels pretty hostile for you to not support MacPorts #7361 and also not have a .pkg.

FWIW, MacPorts has a py-awscli package which we do use.

breiter commented 2 years ago

I can't believe this issue has been open for more than 2 1/2 years.

Problems like #20047 are a direct result of not supporting the native redistributable Apple package format. Homebrew as the only official distribution mechanism for azure-cli on macOS is obnoxious. As noted by the OP, we should not have to install brew just to install azure-cli. I understand if you don't want to create a package for Homebrew or whatever but .pkg is the native redistributable format for macOS.

If the installer script is the only escape hatch from Homebew for macOS, it should be bulletproof and tested on all recent versions. If that seems onerous, perhaps just packaging az as a .pkg would be the obvious solution. Then it can be distributed by double-click, something like sudo installer -pkg az-cli.pkg -target /, and management systems like JAMF or maybe Microsoft InTune.

It's an enormous pain that az is not easy to install on macOS and carries a dependency of either brew or python script debugging.

jhdxr commented 2 years ago

There is always a reason why azure is behind aws.

Related issue is created 4 years ago, and rejected by the azure team arrogantly. Installing with homebrew is still the ONLY official support way to install azure cli. (the doc clearly states for the catch-all bash script

Note that this process is not officially maintained to be compatible with macOS.

)

Do you guys think we don't use homebrew is just because we don't know/have homebrew?

sammysheep commented 1 year ago

As another point for this, I would be willing to use brew if it wouldn't cause issues with my existing MacPorts installation. Using them side-by-side is thought to lead to unwanted interactions. Grateful for the all the work that has been done so far, please keep supporting MacOS!

wUEZRs commented 1 year ago

We're also facing trouble now, wanting clientless VPN for our Macs. Alas, the brew is a roadblock.

janparttimaa commented 7 months ago

These guys might help you with creating official PKG-installer: https://macadmins.software/slack.html