Azure / Azure/bicep-registry-modules

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

Open
#4,036 6 comments 0 reactions 1 assignee Claimed by @JPEasier View on GitHub
Class: Resource Module :package: Needs: Immediate Attention :bangbang: Needs: Triage :mag: Status: Response Overdue :triangular_flag_on_post: Type: AVM :a: :v: :m: Type: Feature Request :heavy_plus_sign:
Dominant language
Bicep
Stars
736
Forks
564
Avg merge
3d 15h
Merged PRs (30d)
30

Description

### Check for previous/existing GitHub issues

- [x] 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](https://learn.microsoft.com/en-us/azure/container-registry/tutorial-enable-customer-managed-keys#create-a-container-registry), 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_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.