search

Azure / bicep-registry-modules

Bicep registry modules
MIT License
513 stars 362 forks source link

[Failed pipeline] avm.res.service-networking.traffic-controller #3702

Closed avm-team-linter[bot] closed 2 weeks ago

avm-team-linter[bot] commented 3 weeks ago

Failed run: https://github.com/Azure/bicep-registry-modules/actions/runs/11607584585

avm-team-linter[bot] commented 3 weeks ago

[!IMPORTANT] @Azure/avm-res-servicenetworking-trafficcontroller-module-owners-bicep, the workflow for the avm/res/service-networking/traffic-controller module has failed. Please investigate the failed workflow run. If you are not able to do so, please inform the AVM core team to take over.

avm-team-linter[bot] commented 2 weeks ago

Failed run: https://github.com/Azure/bicep-registry-modules/actions/runs/11643154439

microsoft-github-policy-service[bot] commented 2 weeks ago

[!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)!