capabilities.work

Shift Revision Traffic

A 3-step recipe with Azure Container Apps. We can help you get access.

Recipe · 3 steps

Shift Revision Traffic

with Azure Container Apps · IT Infrastructure Management

Route all ingress traffic to one revision and confirm the change applies.

  1. List the app's revisions to confirm the target revision exists before shifting traffic to it.
  2. Patch the app ingress traffic so the target revision receives all weight, supplied in the ARM properties envelope.
  3. Read the container app and check its provisioningState, looping while the traffic change is still applying and ending once it settles.
What you'll need to have ready
  • subscriptionId: The Azure subscription ID.
  • resourceGroupName: The name of the resource group.
  • containerAppName: The name of the container app.
  • location: The Azure region of the app (e.g. eastus).
  • targetRevisionName: The revision that should receive all ingress traffic.
  • apiVersion: Client API version.
For your developer

Arazzo workflow azure-container-apps:shift-revision-traffic, 3 operations: ContainerAppsRevisions_ListRevisions → ContainerApps_Update → ContainerApps_Get. Specs on APIs.io.

More recipes with Azure Container Apps

Activate Latest RevisionAudit App SecurityDecommission AppDeploy App Into New EnvironmentEnable Dapr SidecarProvision and Run JobProvision Container AppProvision Managed EnvironmentRestart Active RevisionRotate and Verify Secrets