That's right folks! You are reading that correctly. On the 21st of May the Azure Verified Modules Microsoft Team will be hosting an external community call in which contributors, consumers and people with a general interest can attend! The calls will be scheduled on a quarterly basis alternating between EMEA, APJ & Americas time zones to make sure we can capture the majority of our wonderful community.
Register Today!
AVM External Community Call - 21st May 2024 · Issue #859 · Azure/Azure-Verified-Modules (github.com)
As customers are facing challenges of ensuring their workloads are resilient and reliable in the face of unpredictable events, AVM is adapting as one of the tools that customers can leverage to proactively improve the reliability and resiliency of their workloads inline with the Well-Architected Framework, Reliability Hub and Azure Proactive Reliance Library.
With this in mind the AVM Team has updated the 'What does AVM mean by "WAF Aligned" Section on our site and we are actively engaging in ensuring we have module alignment across both Bicep and Terraform. So....Whats been done so far?
Within the CI Framework for Azure Verified Modules, both Bicep & Terraform have been updated to specifically test against the reliability pillar of the well-architected framework by default (Where there is no external dependency).
For Terraform an Automated Testing Framework has been built to support WAF alignment using TFLint by our core-team and Terraform Engineering Team, the framework is continually expanding its rule-set to ensure the rules for each resource are included.
With Bicep we are leveraging the partnership from the AVM Core Team with the PS Rule to ensure we are capturing the latest tests from the latest baselines.
Integration with our tooling to make sure our examples and defaults align with the expected outcome of a reliable resources is key to ensuring we have our modules "fully tested" meaning if any of these tests fail, we will not publish any new versions until the tests are passing.
The AVM team are excited that our community have been busy building AVM Modules. As of April 30th the AVM Footprint currently looks like:
Language |
Published |
In development |
Bicep |
132 |
22 |
Terraform |
36 |
61 |
Full list of Bicep Resource Modules are available here: AVM Bicep Resource Index
aad/domain-service |
healthcare-apis/workspace |
load-test-service/load-test |
managed-services/registration-definition |
network/application-gateway |
application-gateway-web-application-firewall-policy |
network/network-watcher |
service-fabric/cluster |
sql/instance-pool |
sql/managed-instance |
Full list of Bicep Resource Modules are available here: AVM Bicep Pattern Index
authorization/policy-assignment |
authorization/role-assignment |
policy-insights/remediation |
security/security-center |
Full list of Terraform Resource Modules are available here: AVM Terraform Resource Index
kusto/cluster | servicebus/namespace |
Full list of Terraform Resource Modules are available here: AVM Terraform Resource Index
aks/production |
Well folks! That's it from Azure Verified Modules Team. If you missed the update from last month, you can find that here AVM - March Updates BlogPost. 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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.