search

Azure / bicep-registry-modules

Bicep registry modules
MIT License
421 stars 277 forks source link

[AVM Module Issue]: Container Registry Module should add the creation of `Microsoft.ContainerRegistry/registries/scopeMaps` #2609

Open NanaXiong00 opened 5 days ago

NanaXiong00 commented 5 days ago

Check for previous/existing GitHub issues

Issue Type?

Feature Request

Module Name

avm/res/container-registry/registry

(Optional) Module Version

No response

Description

Please add the creation of Microsoft.ContainerRegistry/registries/scopeMaps.

For example (azd):

CC: @jongio

(Optional) Correlation Id

No response

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.

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

@NanaXiong00, thanks for submitting this issue for the avm/res/container-registry/registry module!

[!IMPORTANT] A member of the @Azure/avm-res-containerregistry-registry-module-owners-bicep or @Azure/avm-res-containerregistry-registry-module-contributors-bicep team will review it soon!

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