You might not need 'jq' for simpler use cases

I wanted to find out how other people use the AZURE_CONFIG_DIR environment variable¹ and I came across a rather ingenious way² to not rely on JQ³ for working with JSON in simpler use cases:

1
2
3
4
5
6

jq() {
    echo -n "$1" | python3 -c "import json, sys; print(json.load(sys.stdin)${2})"
}

$ jq "$(cat ~/.azure/azureProfile.json)" "['subscriptions'][0]['name']"
tst002

This is wholly unnecessary when working Azure CLI as that already has the --query option for defining a JMESPath⁴ query, but could still be useful nonetheless in more constrained environments.