Replies: 1 comment
-
Specifically, you can choose what to do with resources in your stack/bicep config when you no longer want to manage them. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using Azure Bicep to create Resource Groups and Resources across two different Azure Subscriptions. Therefore, my root / top-level Bicep template has a
targetScope = 'subscription'
.The link below talks about using the
Complete
deployment mode to delete Azure resources that were provisioned with Bicep.However, when you're deploying to the
subscription
scope, theNew-AzSubscriptionDeployment
PowerShell command does not have a-DeploymentMode
parameter.#8504
This documentation about ARM Deployment Modes does not mention anything about
scope
.So, the question is ... if you're deploying Bicep to the
subscription
scope, how do you perform aComplete
deployment that deletes resources that are no longer defined in the Bicep template?Beta Was this translation helpful? Give feedback.
All reactions