Support using an existing container registry

[davidfowl]

Today azd up will provision a container registry as part of the ACA environment. It should be possible to use a different container registry with the container apps environment.

That would mean that we need to support setting up the managed identity with an existing container registry to make sure pulling works.

[rajeshkamal5050]

@ellismg as part of AKS/ACA enhancements @wbreza has added support for referencing existing container registry

Can we leverage/re-surface it in the context of Aspire too?

[davidfowl]

This also applies to the container apps environment

[rajeshkamal5050]

Adding to next semester i.e., post GA feature. cc @vhvb1989 @ellismg @davidfowl

[davidfowl]

So there'll be no way to avoid creating a container registry

[rajeshkamal5050]

So there'll be no way to avoid creating a container registry

@vhvb1989 @ellismg any way to control this elegantly? or have to infra synth, modify bicep to use existing container registry?

[Trubador]

I second this feature since otherwise a container registry will be created for each container app and this is a waste of resources and money. Is it possible to change this manually?

[onionhammer]

Any movement on this issue?

[davidfowl]

This should be supported with https://github.com/dotnet/aspire/issues/9005

var acr = builder.AddAzureContainerRegistry("acr").PublishAsExisting(rg, name);

builder.AddAzureContainerAppEnvironment("env")
       .WithAzureContainerRegistry(acr);