azure-cli VS PowerShell

If you don't use AWS, you can usually find CLI tools for other major cloud infrastructure services, such as Azure CLI or gcloud CLI.

Yep. They also do not notice, that Fedora 37 is using Python 3.11 already, and can't merge the fix for azure-cli for 2 months to fix the compatibility issue: https://github.com/Azure/azure-cli/pull/24109

References: https://github.com/Azure/azure-cli/issues/20476

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...

Isn't Azure CLI written in Python?

Even though it seems like a pretty good little hack – this is not supported. The Portal would also bug out and refuse to display Environments correctly if the resource were created with “Other” workflow:

msiexec.exe /package https://github.com/PowerShell/PowerShell/releases/download/v7.2.6/PowerShell-7.2.6-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1 USE_MU=1 ENABLE_MU=1 ADD_PATH=1

This smells like when PowerShell aliased curl and wget to a completely different command, with incompatible arguments.

https://github.com/PowerShell/PowerShell/pull/1901

PowerShell is available on macOS and Linux as well (source on Github: https://github.com/PowerShell/PowerShell). It may not be as well-integrated with things like system services management, but the language still works well. You can still use all the command line tools you're used to on Linux, of course.

nushell does look interesting, though the lack of a .deb repository does put it pretty low on my to-do list.

Issue #7940 discusses potential improvements to array slicing.

Note: This can be problematic as it prevents upstream commands from running their end {} block. See here. The new clean {} block introduced in PowerShell v7.3 does not suffer from this issue.

Can you give an example of something that PS can do that is built-in for text processing, instead of a proprietary symbolic query language?

[1] https://github.com/PowerShell/PowerShell

https://github.com/PowerShell/PowerShell/blob/master/LICENSE... is the MIT license. (Microsoft supplies debs directly which may reduce the motivation for Debian to do so.)

Oh, heh, also https://github.com/PowerShell/PowerShell/blob/master/docs/bu... the build script is written in PowerShell, so there's a bootstrapping problem :-) (Debian has solved those before of course, but with community sentiment like the above maybe noone is motivated to bother.)

According to https://github.com/PowerShell/PowerShell/issues/19628, the default behaviour is invoked whenever the completion script returns no output. To attempt to do so, I tried exiting the script via returning an empty string, or using the return keyword to exit the script completely, unfortunately with no avail. Is there a technique to achieve what I want, and is there any documentation about it other than the official one? Thank you in advance.