[AVM Module Issue]: unable to create a container-registry/registry with actually using credentialSets and cacheRules

[KLuuKer]

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

I'm unable to make a container registry that has cacheRules but also a credentialSets properly configured with just using the module itself.

As a user i want to use a single module to do "everything" for me. (me having to first precreate a keyvault is fine and acceptable)

i DONT want to:

• make a ACR first
• create a credentialSet manually
• and then still have to also manually setup the cacheRules

    cacheRules: [
      {
        credentialSetResourceId: '<credentialSetResourceId>'  <<< how do i get this from my credentialSets input down below????
        name: 'customRule'
        sourceRepository: 'docker.io/library/hello-world'
        targetRepository: 'cached-docker-hub/hello-world'
      }
    ]
    credentialSets: [
      {
<<< i dont want to have to create this inside some other hacky resource\module reference that also requires me to have a already existing ACR
        authCredentials: [
          {
            name: 'Credential1'
            passwordSecretIdentifier: '<passwordSecretIdentifier>'
            usernameSecretIdentifier: '<usernameSecretIdentifier>'
          }
        ]
        loginServer: 'docker.io'
        managedIdentities: {
          systemAssigned: true
        }
        name: 'default'
      }
    ]

(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]

@KLuuKer, 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)!