Which product(s) are you raising for?
ALZ PowerShell Module (Accelerator)
What versions of the tools are you using?
AZ PowerShell Version: 15.5.0
Alz-bicep-accelerator v1.0.6
What is the bug?
The Core-Logging step in pipeline "02 Azure Landing Zones Continuous Delivery" fails with error "GlobalResourceLock' is not defined in the template".
This is caused by bug [AVM Module Issue]: Duplicate lock resource names cause InvalidTemplate error in Deployment Stacks Azure/bicep-registry-modules#6794
Solution is to bump the version of module avm/ptn/alz/ama/ to 0.2.0 see https://github.com/Azure/bicep-registry-modules/releases/tag/avm%2Fptn%2Falz%2Fama%2F0.2.0, after bumping the version from 0.1.1 to 0.2.0 the pipeline successfully completes.
Log Output
The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Deployment stack failed with error: 17:57:35 - The deployment 'alz-core-logging-26040717gmq8f' failed with error(s). Showing 1 out of 1 error(s).
Status Message: Deployment template validation failed: 'The resource 'Microsoft.Insights/dataCollectionRules/dcr-vmi-alz-westeurope/providers/Microsoft.Authorization/locks/GlobalResourceLock' is not defined in the template. Please see https://aka.ms/arm-syntax for usage details.'. (Code:InvalidTemplate)
Screenshot(s)
No response
Which product(s) are you raising for?
ALZ PowerShell Module (Accelerator)
What versions of the tools are you using?
AZ PowerShell Version: 15.5.0
Alz-bicep-accelerator v1.0.6
What is the bug?
The Core-Logging step in pipeline "02 Azure Landing Zones Continuous Delivery" fails with error "GlobalResourceLock' is not defined in the template".
This is caused by bug [AVM Module Issue]: Duplicate lock resource names cause InvalidTemplate error in Deployment Stacks Azure/bicep-registry-modules#6794
Solution is to bump the version of module avm/ptn/alz/ama/ to 0.2.0 see https://github.com/Azure/bicep-registry-modules/releases/tag/avm%2Fptn%2Falz%2Fama%2F0.2.0, after bumping the version from 0.1.1 to 0.2.0 the pipeline successfully completes.
Log Output
Screenshot(s)
No response