Conversation
Deploying localstack-docs with
|
| Latest commit: |
0924625
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0a4241df.localstack-docs.pages.dev |
| Branch Preview URL: | https://harshmishra-doc-81.localstack-docs.pages.dev |
| - filter by type: `where type =~ 'Microsoft.Web/sites'` | ||
| - filter by type and name: `where type =~ 'Microsoft.Web/sites' and name =~ 'ls-app-doc81'` | ||
| - filter by name: `where name =~ 'ls-app-doc81'` | ||
| - project only IDs: `where type =~ 'Microsoft.Web/sites' and name =~ 'ls-app-doc81' | project id` |
There was a problem hiding this comment.
Is it worth pointing out the known limitations here?
For example:
| - project only IDs: `where type =~ 'Microsoft.Web/sites' and name =~ 'ls-app-doc81' | project id` | |
| The following queries are all supported: | |
| - filter by type: `where type =~ 'Microsoft.Web/sites'` | |
| - filter by type and name: `where type =~ 'Microsoft.Web/sites' and name =~ 'ls-app-doc81'` | |
| - filter by name: `where name =~ 'ls-app-doc81'` | |
| - project only IDs: `where type =~ 'Microsoft.Web/sites' and name =~ 'ls-app-doc81' | project id` | |
| - | |
| Known limitations: the Localstack for Azure emulator currently does not support the following constructs: | |
| - nested queries | |
| - the `count` keyword | |
| - the `extend` keyword | |
| - the `join` keyword | |
| - the `limit` keyword | |
| - the `mv-expand` keyword | |
| - the `order` keyword | |
| - the `parse` keyword | |
| - the `project-away` keyword | |
| - the `sort` keyword | |
| - the `summarize` keyword | |
| - the `take` keyword | |
| - the `top` keyword | |
| - the `union` keyword |
For reference, the full list of operators can be found here:
https://learn.microsoft.com/en-us/azure/governance/resource-graph/concepts/query-language#supported-tabulartop-level-operators
Considering we only support a small subset of this list, it could also be easier to only show the constructs that we do support!
There was a problem hiding this comment.
@HarshCasper / @bblommers, while using az rest to call the Azure Resource Graph is perfectly doable, it's very unusual. Users prefer to install to the az extension resource-graph as follows:
az extension add --name resource-graphand use it as shown in Quickstart: Run Resource Graph query using Azure CLI
az graph query --graph-query 'Resources | project name, type | limit 5'
az graph query --graph-query 'Resources | where type =~ 'Microsoft.Storage/storageAccounts' | project name, location`
...I strongly suggest to refactor the article to use az graph. Said that, I would also keep the az rest you and Bert created to show readers an additional method to invoke the Azure Resource Graph API in Azure as well as our emulator.
I realized that the current implementation throws exceptions with some licit queries, so we need to fix the codebase. I'll take this offline with Bert.
cc: @quetzalliwrites
Fixes DOC-81