Closed maciejporebski closed 2 years ago
Thanks for reporting this! We should have a fix available in the next couple weeks.
This should now be fixed in all regions - a GET of deploymentStacks at subscription scope should now return an empty array. Let us know if you see any further issues. Thanks!
Describe the bug
Get-AzSubscriptionDeploymentStack
command andGET /subscriptions/${SubscriptionId}/providers/Microsoft.Resources/deploymentStacks?api-version=2021-05-01-preview
return 429 TooManyRequests if no subscription scoped stacks exist. This in turn results in theGet-AzSubscriptionDeploymentStack
command hanging as it enters a retry loop which continuously receives 429 responses. In my test environment I was also unable to exit out of the command and had to close the shell.To Reproduce Steps to reproduce the behavior:
Get-AzSubscriptionDeploymentStack
commandRepro script used (script output below): (Instead of using the Get-AzSubscriptionDeploymentStack command in the retro script the API endpoint is called directly as -Debug does not appear to return any useful information before it hangs, example of that included below)
Expected behavior An empty result is returned. (Same as the behaviour of Get-AzResourceGroupDeploymentStack)
Screenshots N/A
Repro Environment Host OS: Windows 11 (22499.1010) Powershell Version:
Server Debugging Information Correlation ID: 93dfa910-6a50-43a5-b8c1-0c893ba5249f Tenant ID: 5c162c0f-ddd8-49d9-9933-f99540d7ec74 Subscription ID: 9cc55246-7157-4ef7-a375-ce22fb559f66 Timestamp of issue (please include time zone): Tue, 16 Nov 2021 23:12:22 GMT Data Center (eg, West Central US, West Europe): UKSOUTH
Additional context
Output of Get-AzSubscriptionDeploymentStack -Debug
Repro script output: