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
Azure Elastic SAN for Azure VMware Solution: now Generally Available
Have you been looking to expand your storage on Azure VMware Solution (AVS), but do not need the extra compute performance and the associated ...
Introducing Pull Request Annotation for CodeQL and Dependency Scanning in GitHub Advanced Security for Azure DevOps
In the world of software development, security is paramount. As developers, we strive to write clean, efficient, and most importantly, secure ...
Accelerate metadata heavy workloads with Metadata Caching preview for Azure Premium Files SMB & REST
Azure Files previously announced the limited preview of Metadata caching highlighting improvements on the metadata latency (up to 55...
How to Choose the Right Models for Your Apps | Azure AI
With more than 1700 models to choose from on Azure, selecting the right one is key to enabling the right capabilities, at the right price poin...
MMR Call Redirection for Azure Virtual Desktop, Windows 365 now available
Today, I am pleased to share the launch of Multimedia Redirection (MMR) Call Redirection for Azure Virtual Desktop and Windows 365. Call Redir...
Liquid Cooling in Air Cooled Data Centers on Microsoft Azure
With the advent of artificial intelligence and machine learning (AI/ML), hyperscale datacenters are increasingly accommodating AI accelerators...
Introducing Azure Product Retirement Livestreams
The Azure Retirements team, in collaboration with key partner groups, is excited t...
Azure Developer CLI (azd) – October 2024
This post announces the October release of the Azure Developer CLI (`azd`), including configurable api-version for ACA. The post Azure Develop...
[Solved] Azure Function is not showing in the List in Azure Function App in Portal after Published from Visual Studio
While working with Azure Function and Publishing to Azure, you may find that your function gets published from Visual studio but your function...