fix: Moved Databricks removal into explicit removal (before RG) for managed resource removal #1872
Conversation
…ts.ps1 Co-authored-by: Erika Gressi <56914614+eriqua@users.noreply.github.com>
…ts.ps1 Co-authored-by: Erika Gressi <56914614+eriqua@users.noreply.github.com>
…hr/bicep-registry-modules into users/workflowRetire
feat: Added deployment removal workflow
…auses managed rgs to be removed too
microsoft-github-policy-service
bot
added
the
Needs: Triage 🔍
|
Important The "Needs: Triage 🔍" label must be removed once the triage process is complete! Tip For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation. Note This label was added as per ITA06. |
|
Note The "Type: AVM |
microsoft-github-policy-service
bot
added
the
Type: AVM 🅰️ ✌️ Ⓜ️
| @@ -92,6 +92,7 @@ function Initialize-DeploymentRemoval { | |||
| 'Microsoft.Compute/virtualMachines', | |||
| 'Microsoft.VirtualMachineImages/imageTemplates', # Must be removed before their MSI | |||
| 'Microsoft.ManagedIdentity/userAssignedIdentities', | |||
| 'Microsoft.Databricks/workspaces', | |||
There was a problem hiding this comment.
Like the pipeline failed? Or the RGs remained? My 3 tests so far worked, but each time the Databricks deployment itself had issues
There was a problem hiding this comment.
The RG remained. Let's maybe see if the behavior changed and this workaround works now. If still not, as discussed, we can work on a custom post removal logic.
There was a problem hiding this comment.
Re-running one last time in the hopes that it's not getting stuck on the dependency issue again - like for the last 4 times.
There was a problem hiding this comment.
Can't get around the issue during the deployment. Will close the PR for now
Description
Moved Databricks removal into explicit removal (before RG) for managed resource removal
Fixes #1581
Pipeline Reference
Type of Change
version.json:version.json.version.json.