Azure Verified Modules - Monthly Update [June]
AVM Module Summary
The AVM team are excited that our community have been busy building AVM Modules. As of June 17th, the AVM Footprint currently looks like:
Language |
Published |
In development |
Bicep |
214 |
49 |
Terraform |
44 |
24 |
Bicep Resource Modules Published in June:
Full list of Bicep Resource Modules is available here: AVM Bicep Resource Index
avm/res/portal/dashboard |
avm/res/kusto/cluster |
avm/res/hybrid-compute/machine |
avm/res/alerts-management/action-rule |
Bicep Pattern Modules Published in June:
Full list of Bicep Resource Modules is available here: AVM Bicep Pattern Index
avm/ptn/lz/sub-vending |
General Bicep Updates
- There are currently 36 Bicep modules proposed (actively being worked on or looking for owners).
- Providing documentation of Input Parameter usage has been in the documentation for some time. The provided examples are now also rendered into the readmes for modules. Module owners can simplify adopting modules to certain usage scenarios, like an Azure Queue for triggering a job.
Terraform Resource Modules Published in June:
Full list of Terraform Resource Modules is available here: AVM Terraform Resource Index
avm-res-network-networkwatcher |
Terraform Pattern Modules Published in June:
Full list of Terraform Resource Modules is available here: AVM Terraform Resource Index
avm-ptn-network-private-link-private-dns-zones |
avm-ptn-network-routeserver |
General Terraform Updates
- There are currently 115 Terraform modules proposed (actively being worked on or looking for owners).
General AVM Site Updates
- TF Module review process – New article created to detail the steps of the mandatory initial review of Terraform modules. This guides modules owners through the process of the initial code review that needs to take place prior to publishing a new Terraform modules. (ref)
That's A Wrap!
Well folks! That's it from Azure Verified Modules Team. If you missed the update from last month, you can find that here AVM - May Updates Blog. Other than that, as always, we want to say a massive thank you to our community and our teams continued efforts to develop and collaborate.
Published on:
Learn moreRelated posts
Episode 397 – Local LLMs: Why Every Microsoft 365 & Azure Pro Should Explore Them
Welcome to Episode 397 of the Microsoft Cloud IT Pro Podcast. In this episode, Scott and Ben dive into the world of local LLMs—large language ...
Integrating Azure OpenAI models in your Projects: A Comprehensive Guide
In the previous blog, we have explored how to install and configure Azure OpenAI Service, now we will be unlocking its potential further by in...
Effortless Scaling: Autoscale goes GA on vCore-based Azure Cosmos DB for MongoDB
We’re thrilled to announce that Autoscale is now generally available (GA) for vCore-based Azure Cosmos DB for MongoDB! Say goodbye to manual s...
Making MongoDB workloads more affordable with M10/M20 tiers in vCore-based Azure Cosmos DB
vCore based Azure Cosmos DB for MongoDB is expanding its offerings with the new cost-effective M10 and M20 tiers for vCore-based deployments. ...
Replacing jackson-databind with azure-json and azure-xml
This blog post explains how azure-json and azure-xml replaced jackson-databind in the Azure SDK for Java. The post Replacing jackson-databind ...
March Patches for Azure DevOps Server
Today we are releasing patches that impact our self-hosted product, Azure DevOps Server. We strongly encourage and recommend that all customer...
Implementing Chat History for AI Applications Using Azure Cosmos DB Go SDK
This blog post covers how to build a chat history implementation using Azure Cosmos DB for NoSQL Go SDK and langchaingo. If you are new to the...