azure-cli VS yq

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:

What I often use to just get the full key paths is yq (https://github.com/mikefarah/yq), piping into grep when necessary

  yq -o=props 

For more information about this command visit https://github.com/mikefarah/yq

I've been trying to install and config a plugin (papis.nvim) for a couple of days and am having issues with a function that uses io.popen to run yq to convert yaml files to json. I know my install of yq is fine- I can run yq -oj info.yaml from the command line with no issue and it produces the correct json output. I know the function can find the yq executable, but it returns nil. I've saved the error from the yq golang code: panic: runtime error: invalid memory address or nil pointer dereference

- yq has no if-then-else https://github.com/mikefarah/yq/issues/95 which is a poor design (or omission) in my opinion

After which, I use openapi-generator to make a yaml output.

https://gist.github.com/freshteapot/3637e8d2b5ecdf01b7d25246...

- yq version 3.4.1 (Worth noting, the example uses an out of date yq, so a few modifictaions might be needed)

https://github.com/mikefarah/yq

For those pining for a similar yaml query tool for working through acres of config: https://github.com/mikefarah/yq

jq is awesome and thanks to the new team for their recent efforts and energy, it massively appreciated.

For anyone looking for such a script, there's some CLIs that make it easy. One is `yq -o props` [1], another way is to use `yq -j` or `yj` [2] to convert to JSON and pipe it to `gron` [3].

[1] https://github.com/mikefarah/yq

[2] https://github.com/sclevine/yj

[3] https://github.com/tomnomnom/gron