Azure / Azure/azure-cli

Deployment never completes when deploying bicep file in mode "Complete"

Open
#19,437 3 comments 0 reactions 0 assignees View on GitHub
act-identity-squad ARM customer-reported Service Attention
Dominant language
Python
Stars
4.6k
Forks
3.5k
Avg merge
3d 2h
Merged PRs (30d)
60

Description

> ### `az feedback` auto-generates most of the information requested below, as of CLI version 2.0.62

**Describe the bug**

When using **az deployment group create** command to deploy using a bicep file, the deployment never completes even when all internal bicep modules deployed successfully, it always displays as in progress in the azure portal and as running in the cli
**To Reproduce**

1. Create a simple bicep file that uses other bicep files as modules
2. Run the command similarly as follow:
az deployment group create --subscription "My subscription" --resource-group "MyRg" --parameters env='Dev --template-file main.bicep --mode Complete

**Expected behavior**

Once all the modules that are defined inside main.bicep successfully completes, the main deployment should be marked as completed as well. This has been specially annoying since we need to make sure that if we remove a data factory child from the bicep templates, it should get removed when deploying to azure.

**Environment summary**

az cli version 2.27.2
**Additional context**

This is how it usually looks, in the image i had to cancel it as it passed a really long time still in progress
![image](https://user-images.githubusercontent.com/59450197/131932090-e96f9ce5-ba55-4caa-9f03-50b7b26bc242.png)

And this is how the details of the main deployments look, all the underlying resources deployed aka internal bicep modules deployed fine but the main deployment never completed.

![image](https://user-images.githubusercontent.com/59450197/131932229-2b7d7888-ba6b-467a-a429-448d465a8e43.png)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.