Azure / bicep-registry-modules

Bicep registry modules
MIT License
469 stars 317 forks source link

[Failed pipeline] avm.res.desktop-virtualization.workspace #3306

Open avm-team-linter[bot] opened 5 days ago

avm-team-linter[bot] commented 5 days ago

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

avm-team-linter[bot] commented 5 days ago

[!IMPORTANT] @Azure/avm-res-desktopvirtualization-workspace-module-owners-bicep, the workflow for the avm/res/desktop-virtualization/workspace 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.

microsoft-github-policy-service[bot] commented 5 days ago

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

microsoft-github-policy-service[bot] commented 8 hours 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)!