Introduction Bicep test framework is still in early developmental phase being an experimental feature. It was first presented by Bicep team on the August community call and peaked the interest from the community, myself included. The goal of the test framework is a focus on client-side tests without the need to send off to ARM, …
Introduction There’s a few different options when it comes to consuming Bicep modules, do you need to write your own modules? Use the public Bicep registry? or are there other options to consider? I’ll detail my experiences & thoughts on this with pros & cons that each of the routes have. To check these different …
Testing your Bicep modules with PSRule is a great way to identify that your code is meeting Azure best practice. But how do you actually test your Bicep modules with PSRule properly? How can you structure your Git repository? How can I configure PSRule to test the modules? Can I document what the modules do, …
Introduction Finding a robust validation solution for Bicep has been both straight forward and frustrating. We have amazing tools like PSRule (shout out to Bernie for his incredible tool here) for best practice. And more straight forward ones provided natively by Microsoft such as the Bicep linter. However, the problem in my opinion, when it …
Intro Export template in the Azure Portal is a useful tool to lean on when you need to understand a resources properties, syntaxes, and structure. We’ve all been there, deploying some Bicep or ARM, but it’s failing on some SKU or it doesn’t like some syntax. Whilst the MS Docs are usually fantastic at showing …
No more JSON Parameter files!? Well, nearly. The .bicepparam feature is still in experimental mode currently, but looks to be coming soon as part of the future Bicep releases. If you’ve worked on ARM templates or Bicep you will be very familiar with the joys of working with a JSON parameters file. It can be …