Simon Waight • 9/12/2023

Pushing Azure Infrastructure-as-Code quality left with Bicep

Read Original

This technical article details how to shift quality left in Azure Infrastructure-as-Code (IaC) using Bicep. It covers implementing design-time validation through linting with the Bicep CLI and configuring linter rules via bicepconfig.json files, providing practical examples for structuring projects and managing warnings.

0 comments
#DevOps #validation #Azure
Pushing Azure Infrastructure-as-Code quality left with Bicep

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes