You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/bicep/deployment-stacks.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ Deployment stacks provide the following benefits:
39
39
### Known issues
40
40
41
41
- Deleting resource groups currently bypasses deny assignments. When creating a deployment stack in the resource group scope, the Bicep file doesn't contain the definition for the resource group. Despite the deny assignment setting, it's possible to delete the resource group and its contained stack. However, if a [lock](../management/lock-resources.md) is active on any resource within the group, the delete operation will fail.
42
-
-[What-if](./deploy-what-if.md)isn't available in the preview.
42
+
-The [What-if](./deploy-what-if.md)support is not yet available.
43
43
- A management group-scoped stack is restricted from deploying to another management group. It can only deploy to the management group of the stack itself or to a child subscription.
Use the `action-on-unmanage` switch to define what happens to resources that are no longer managed after a stack is updated or deleted. Allowed values are:
375
375
376
-
deleteAll, deleteResources, detachAll.
377
-
378
376
-`deleteAll`: use delete rather than detach for managed resources and resource groups.
379
377
-`deleteResources`: use delete rather than detach for managed resources only.
380
378
-`detachAll`: detach the managed resources and resource groups.
@@ -518,7 +516,7 @@ Currently not implemented.
518
516
519
517
## View managed resources in deployment stack
520
518
521
-
During public preview, the deployment stack service doesn't yet have an Azure portal graphical user interface (GUI). To view the managed resources inside a deployment stack, use the following Azure Powershell/Azure CLI commands:
519
+
The deployment stack service doesn't yet have an Azure portal graphical user interface (GUI). To view the managed resources inside a deployment stack, use the following Azure Powershell/Azure CLI commands:
522
520
523
521
To view managed resources at the resource group scope:
524
522
@@ -758,8 +756,8 @@ To export a deployment stack at the resource group scope:
758
756
759
757
```azurepowershell
760
758
Save-AzResourceGroupDeploymentStack `
761
-
-Name '<deployment-stack-name>' `
762
-
-ResourceGroupName '<resource-group-name>' `
759
+
-Name "<deployment-stack-name>" `
760
+
-ResourceGroupName "<resource-group-name>" `
763
761
```
764
762
765
763
# [CLI](#tab/azure-cli)
@@ -782,7 +780,7 @@ To export a deployment stack at the subscription scope:
782
780
783
781
```azurepowershell
784
782
Save-AzSubscriptionDeploymentStack `
785
-
-name '<deployment-stack-name>'
783
+
-name "<deployment-stack-name>"
786
784
```
787
785
788
786
# [CLI](#tab/azure-cli)
@@ -804,8 +802,8 @@ To export a deployment stack at the management group scope:
0 commit comments