Provision and Run Job
A 3-step recipe with Azure Container Apps. We can help you get access.
Recipe · 3 steps
Provision and Run Job
with Azure Container Apps · IT Infrastructure Management
Create a manual job, wait for it to provision, and start an execution.
- Create a manually triggered job bound to the environment, defining its trigger configuration and a single container in the ARM properties envelope.
- Read the job and check its provisioningState, looping while it is still in progress and proceeding once it reaches Succeeded.
- Start a single execution of the provisioned job, overriding the template image for this run.
What you'll need to have ready
- subscriptionId: The Azure subscription ID.
- resourceGroupName: The name of the resource group.
- jobName: The name of the job to create.
- environmentId: Resource ID of the managed environment that hosts the job.
- location: The Azure region for the job (e.g. eastus).
- image: The container image the job runs to completion.
- replicaTimeout: Maximum number of seconds a replica is allowed to run.
- apiVersion: Client API version.
For your developer
Arazzo workflow azure-container-apps:provision-and-run-job, 3 operations: Jobs_CreateOrUpdate → Jobs_Get → Jobs_Start. Specs on APIs.io.