Description
Based on the REST API Crawler IP (which is also embedded in the REST2CARML work) we could generate a ProviderNamespace-ResourceType-API file (e.g. JSON) that contains all available permutations.
For example
{
"Microsoft.Storage" {
"storageAccounts": [
"2020-06-01",
"2021-06-01",
"(..)"
],
"storageAccounts/blobServices": [
"2020-06-01",
"2021-06-01",
"(..)"
],
"(..)"
},
"(..)"
}
This file could be generated in a daily pipeline run and made available in our respository - essentially allowing us to maintain our own up-to-date knowledge base.
In the past it showed that the Get-AzResourceProvider function does not provide consistent results - in cases blocking PRs.
Description
Based on the REST API Crawler IP (which is also embedded in the REST2CARML work) we could generate a ProviderNamespace-ResourceType-API file (e.g. JSON) that contains all available permutations.
For example
{ "Microsoft.Storage" { "storageAccounts": [ "2020-06-01", "2021-06-01", "(..)" ], "storageAccounts/blobServices": [ "2020-06-01", "2021-06-01", "(..)" ], "(..)" }, "(..)" }This file could be generated in a daily pipeline run and made available in our respository - essentially allowing us to maintain our own up-to-date knowledge base.
In the past it showed that the
Get-AzResourceProviderfunction does not provide consistent results - in cases blocking PRs.