Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
1 task done
KLuuKer opened this issue Nov 24, 2024 · 2 comments
Assignees
Labels
Class: Resource Module 📦 This is a resource module Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Feature Request ➕ New feature or request

Comments

@KLuuKer
Copy link

KLuuKer commented Nov 24, 2024

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

@KLuuKer KLuuKer added Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue labels Nov 24, 2024

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.

Copy link

@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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Class: Resource Module 📦 This is a resource module Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Feature Request ➕ New feature or request
Projects
Status: Needs: Triage
Development

No branches or pull requests

2 participants