azure-cli

> It’s pretty clear if you check github that Azure’s services and documentation are written by distributed teams with little coordination. I've come to the same conclusion after dealing (and reporting) jankyness in both the Azure (ARM) API and especially the CLI. [0] is a nice issue I look at every once in a while. I think an installed az cli is now 700 MB+ of Python code and different bundled python versions... [0]: https://github.com/Azure/azure-cli/issues/7387

> So let's vendor it. How much code is there? After removing all tests, we end up with 29 individual crates vendored taking up 62MB disk space. Tokei reports 209,150 lines of code. > Now this is a bit misleading, because like many times most of this is within windows-. But how much of windows- does getrandom need? A single function. See also the Azure CLI. There's a github issue, still open, from 2018 complaining about their 350 MB monstrosity bloating up a docker container. By now the thing weighs more than 1.5 GB. Fucking MS. https://github.com/Azure/azure-cli/issues/7387

In the spirit of moto, it actually looks like quite a bit of the groundwork is available for someone to take a swing at an Azure version: * the cli uses the python SDK: https://github.com/Azure/azure-cli/blob/azure-cli-2.38.0/src... * which uses autorest: https://github.com/Azure/azure-sdk-for-python/tree/azure-mgm... * of what appears to be an OpenAPI-ish spec: https://github.com/Azure/azure-rest-api-specs/tree/fda2db441...

Yes, as a 10-year user of Tumbleweed, generally OpenSUSE is left behind when it comes to downloading binary packages from first-party sources. Even for the Microsoft software that "supports" OpenSUSE, historically that support was by expecting OpenSUSE users to use their RHEL packages which didn't always work well. [1] [2] (I don't know if the problems are still there, because I switched to the Docker image for `az` and stopped using `powershell`) [1]: https://github.com/PowerShell/PowerShell/issues/6184 [2]: https://github.com/Azure/azure-cli/issues/7523

It's not as bad, but the script used to build deb package for azure-cli is a bit weird and not really a thing of beauty: https://github.com/Azure/azure-cli/blob/dev/build_scripts/de...

[msft] :). Interestingly enough, the decision to use linux/docker was a no-brainer. I know from the outside it might seem odd, but these days, the attitude (and rightly so) is: use the language/stack/OS/toolchain/etc. you need to get your job done. I think you'll see an explosion of Linux/Python/Java/Go/... internally & externally on Azure. Data point - our team (Python), wanted to hold a "Python day @ msft" event to teach/inform internal teams on the language/ecosystem. We were hoping maybe 50..100 would show up, if lucky. A thousand and twenty one people showed up! Another data point - the official Azure CLI was just rewritten in Python (win/macos/linux): https://github.com/Azure/azure-cli Thanks!

Azure also uses this in their new CLI [0]. The biggest advantage of JMESPath over jq is that JMESPath is a spec, and thus can be implemented in several languages [1]. [0]: https://github.com/Azure/azure-cli [1]: http://jmespath.org/libraries.html

Thanks, we updated the link from https://github.com/Azure/azure-cli.

Funny enough, I use Python primarily, but when it comes to deploying small standalone tools I have a list of things I want to rewrite into something like Go so I don't have to deal with dependencies. In my little experience with Node it seems even worse. One petty but relevant fact is that Node isn't installed by default while Python generally is. I can definitely see prototyping something in whatever language is convenient and after proving its usefulness rewrite it in a language that fits wider goals. Their motivation[1] seems pretty solid. [1] https://github.com/Azure/azure-cli/wiki/Motivation

Looks like the are going for both 2 and 3 support? https://github.com/Azure/azure-cli/blob/master/scripts/dev_s... EDIT: Nah, only 3. So much for Microsoft and it's legendary backwards compatibility. https://github.com/Azure/azure-cli/blob/master/scripts/gener...

motivation: - Dependency management for Node.js adds maintenance costs for Linux distributions. - Cloud tooling vendors prefer Python to match AWS CLI and GCloud CLI. - Python offers a more mature platform for building CLIs Python is typically available on Linux distributions by default. - While none of these reasons precluded building the next CLI in Node.js, Python was the natural choice. taken from here - https://github.com/Azure/azure-cli/wiki/Motivation

Answers: https://github.com/Azure/azure-cli/wiki/Motivation