Open avm-team-linter[bot] opened 3 weeks ago
[!WARNING] This issue couldn't be assigend due to an internal error. @fbinotto, please make sure this issue is assigned to you and please provide an initial response as soon as possible, in accordance with the AVM Support statement.
[!WARNING] This issue couldn't be assigend due to an internal error. @fbinotto, please make sure this issue is assigned to you and please provide an initial response as soon as possible, in accordance with the AVM Support statement.
[!IMPORTANT] The "Needs: Triage :mag:" label must be removed once the triage process is complete!
[!TIP] For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.
[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.
[!TIP]
- To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
- To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!
Failed run: https://github.com/Azure/bicep-registry-modules/actions/runs/9471673764