https://github.com/magodo/azlist

List Azure resources by an Azure Resource Graph `where` predicate.
https://github.com/magodo/azlist

azure

Last synced: 3 months ago
JSON representation

List Azure resources by an Azure Resource Graph `where` predicate.

• Host: GitHub
• URL: https://github.com/magodo/azlist
• Owner: magodo
• License: mpl-2.0
• Created: 2022-09-16T09:39:31.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2024-09-26T11:03:56.000Z (4 months ago)
• Last Synced: 2024-10-13T01:12:06.801Z (4 months ago)
• Topics: azure
• Language: Go
• Homepage:
• Size: 152 KB
• Stars: 4
• Watchers: 3
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# azlist

List Azure resources by an Azure Resource Graph [`where` predicate](https://learn.microsoft.com/en-us/azure/data-explorer/kusto/query/whereoperator).

## Example

```

azlist 'resourceGroup =~ "example-rg"'

```

## FAQ

- **Question**: What is the difference of the resource list returned by `azlist` and ARG?

    

    **Answer**: By default, they are the same. While if `azlist` is called with `--recursive`, it returns more than ARG. The ARG only returns ARM tracked resources, but not for the RP proxy resources (e.g. subnet, network security rules, storage containers, etc). `azlist --recursive` will return all the tracked and proxy resources.

- **Question**: What is the difference of the resource list returned by `azlist --recursive` and ARM template export?

    

    **Answer**: They are meant to be the same. But ARM template export only support some certain falvors (e.g. resource group), while `azlist` allows more. However, `azlist` returns less information for each resource, e.g. it doesn't have the cross resource dependency.

- **Question**: Why predicate `type =~ "microsoft.network/virtualnetworks/subnets"` returns me nothing, even with `--recursive`?

    

    **Answer**: This is because `azlist` will first make an ARG call with the given `where` predicate, then if `--recursive` is specified, it will recursively call the "LIST" on the *known* child resource types. In this case, since the subnet is not an ARM tracked resource, ARG returns nothing. The full list of supported resource types by ARG can be found [here](https://learn.microsoft.com/en-us/azure/governance/resource-graph/reference/supported-tables-resources#resources).

- **Question**: Why isn't any data source listed in my application insight workspace?

    **Answer**: The data source is a proxy resource, which is discovered by listing on its collection API endpoint. However, it requires some special parameters, in this case it is a `$filter = kind eq ` query parameter. Currently, we didn't do any such special handlings for those endpoints (for the sake of maintainance). The same might happens for the other proxy resouce types. To have an overview of resources that hit error during discovery, you can specify the `--print-error`/`-e` option.