The processes described in the Module Support page and Module Lifecycle do not seem to be followed

[alephenne]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Description

The processes (and timelines) described in

• the Module Support page and
• the Module Lifecycle page

do not seem to be followed (for Terraform, at least).

For example, the App Gateway module has issues opened since November that have not even been triaged.
But the module is not indicated as orphaned either. https://github.com/Azure/terraform-azurerm-avm-res-network-applicationgateway/issues.

I think the AVM is a great initiative from Microsoft but if it is advertised as supported by Microsoft, it should be actively supported. This makes it harder to recommend using these modules to customers.

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the AVM Issue Triage documentation.

[mofaizal]

@alephenne Thank you for your feedback and concerns regarding supportability. As the module owner for Application Gateway, I am actively investigating the issue. If you have any questions or need to address any urgent matters, specific issues, or breaking changes, please create an issue in the repository, and I will prioritize it accordingly.