[AVM Module Issue]: Container Registry does not allow auto rotation (using unversioned key uri) on customer managed keys

[mark-vw]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Feature Request

Module Name

avm/res/container-registry/registry

(Optional) Module Version

0.6.0

Description

Per Microsoft Documentation, you can provide either a versioned key URI (for a key that must be rotated manually) or an unversioned key URI (which enables automatic key rotation).

In version 0.6.0, the container registry AVM module does not allow an unversioned key to support the automatic key rotation capability.

Please fix.

Thank you!

(Optional) Correlation Id

No response

[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 BRM Issue Triage documentation.

[avm-team-linter]

@mark-vw, 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]

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 🔍" label must be removed as part of the triage process (when the issue is first responded to)!