How One Developer Decided What Custom Azure Bicep Work to Keep After AVM Emerged
A developer maintaining custom Bicep modules for Azure faced a critical decision when Azure Verified Modules (AVM) matured into a credible industry baseline. Rather than relying on instinct, they developed a five-step method to systematically sort existing work into three categories: items the standard now handles better, items that still need custom opinion layered on top, and items the standard does not cover at all. The method begins with an honest inventory of owned work, verified against primary sources, before any comparison with the new baseline is made. A key early finding was that two repositories in the candidate set were authored by others and had to be removed, highlighting the importance of establishing provenance. The framework is designed to be domain-agnostic and applicable whenever any authoritative standard — whether a vendor library, managed service, or reference architecture — emerges alongside existing custom work.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in