Importing bicep lint output as test results in Azure DevOps pipelines

Bicep is a great improvement over ARM Templates but doesn’t remove the need to validate our code at build time. I could continue to use the ARM-TTK and validate the generated template, but bicep has it’s own built in rules. Getting build errors in a way that can provide meaningful information in my CI/CD tooling is an interesting challenge. A quick problem description We are using Azure DevOps for build and release automation.

For the full version of this post see Rik Hepworth's personal blog at Importing bicep lint output as test results in Azure DevOps pipelines