Azure / Azure/arm-template-whatif
Deadlock deploying bicep whatif postgre-sql
- Dominant language
- HTML
- Stars
- 101
- Forks
- 21
- Avg merge
- 3h 35m
- Merged PRs (30d)
- 1
Description
**Describe the bug**
See also: https://github.com/Azure/azure-powershell/issues/28487
When deploying a postgres bicep file as Managed Identity with Get-AzSubscriptionDeploymentWhatIfResult the command hangs indefinitely if the target database is stopped.
Using the same file and same command as my Admin user it works.
**To Reproduce**
Steps to reproduce the behavior:
1. Stop Postgres database in Azure
2. WhatIf Deploy a bicep file for the existing database containing a administrators group reference
3. Command hangs indefinitely
4. See error
**Expected behavior**
WhatIf results should be returned
**Screenshots**
See https://github.com/Azure/azure-powershell/issues/28487 for full logs and such.
**Client** [e.g. PowerShell, CLI, API)
PowerShell
**Additional context**
Using Azure DevOps Pipeline and newest bicep and PowerShell Module versions.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reproduction steps in this issue and the linked Azure PowerShell issue for the full logs. Investigate the Get-AzSubscriptionDeploymentWhatIfResult path for a stopped PostgreSQL database deployed with a managed identity and administrators group reference. Done means the what-if results return instead of the command hanging indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100