Allow build pipelines to control which Docker version is active in which clusters

[tjementum]

No description provided.

[tjementum]

There are multiple options to ensure that a new Docker image is pushed to a Cluster.

• Update and deploy Bicep with the tag of the new version

Cons: This requires a deployment of Bicep infrastructure when a new version is deployed. This is not only slow, but introduces race conditions, and adds complexity. Bicep will change all configuration of a cluster.

• Use command line to update the Container App directly

Cons: Will this be overridden when Bicep is deployed, as Bicep is also maintaining this property?

az containerapp update --name account-management-api --resource-group development-west-europe --image "platformplatformdev.azurecr.io/account-management-api:2023.10.24.174" --revision-suffix 2023-10-24-174

• Continuous Deployments

Let webhooks in Container Registry trigger a deployment

Cons: Is it stable, and can you see which version is active.