Now you can filter and transform azd JSON output using JMESPath queries<\/em><\/p>\n The Azure Developer CLI ( Being able to filter and transform JSON output directly in your terminal reduces the need for external tools or manual parsing, enhancing developer productivity. Whether you’re building scripts, automation, or need to inspect a specific part of your noisy config, JMESPath queries offer a simple solution right within the In Output:<\/strong><\/p>\n Output:<\/strong><\/p>\n Output:<\/strong><\/p>\n Explore more query options in the JMESPath documentation<\/a>.<\/p>\n Questions or ideas? File an issue<\/a> or start a discussion<\/a>. Want to help shape Introduced in PR #6664<\/a>. Expanded in PR #6735<\/a>.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" Run JMESPath queries on azd JSON output, including error messages.<\/p>\n","protected":false},"author":63456,"featured_media":3598,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[908,864],"class_list":["post-3597","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure-sdk","tag-azd","tag-azure-developer-cli"],"acf":[],"blog_post_summary":" Run JMESPath queries on azd JSON output, including error messages.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/posts\/3597","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/users\/63456"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/comments?post=3597"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/posts\/3597\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/media\/3598"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/media?parent=3597"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/categories?post=3597"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/tags?post=3597"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nWhat’s new?<\/h2>\n
azd<\/code>) now supports JMESPath<\/a> queries on JSON output, including error messages. Pass --query<\/code> to extract exactly what you need.<\/p>\nWhy it matters<\/h2>\n
azd<\/code> toolset.<\/p>\nHow to use it<\/h2>\n
azd<\/code> versions 1.23.4 or later, --query<\/code> can be used alongside -o json<\/code>, but only with commands that return JSON output.<\/p>\nExamples<\/h3>\n
\n
azd config show -o json --query \"template.sources\"<\/code><\/pre>\n{\r\n \"awesome-azd\": {\r\n \"key\": \"awesome-azd\",\r\n \"location\": \"https:\/\/aka.ms\/awesome-azd\/templates.json\",\r\n \"name\": \"Awesome AZD\",\r\n \"type\": \"awesome-azd\"\r\n }\r\n}<\/code><\/pre>\n<\/li>\nENV_NAME=$(azd env list -o json --query \"[?IsDefault].Name | [0]\")\r\necho \"Deploying to $ENV_NAME\"<\/code><\/pre>\nproduction<\/code><\/pre>\n<\/li>\nazd<\/code> versions 1.23.5 or later, you can extract error messages in automation. For example, when not authenticated and running this command:\nazd auth token -o json --query \"data.message\"<\/code><\/pre>\n\"\\nERROR: not logged in, run `azd auth login` to login\\n\"<\/code><\/pre>\n<\/li>\n<\/ol>\nFeedback<\/h2>\n
azd<\/code>? Sign up for user research<\/a>.<\/p>\n
\n