Deploy App Into New Environment
A 4-step recipe with Azure Container Apps. We can help you get access.
Recipe · 4 steps
Deploy App Into New Environment
with Azure Container Apps · IT Infrastructure Management
Stand up a managed environment and deploy a container app into it end to end.
- Create the managed environment that will host the app, supplying its location in the ARM properties envelope.
- Read the environment and check its provisioningState, looping while it is still being set up and proceeding once it reaches Succeeded.
- Create the container app bound to the new environment id with a single container and external ingress in the ARM properties envelope.
- Read the container app and check its provisioningState, looping while it is still in progress and ending once it settles.
What you'll need to have ready
- subscriptionId: The Azure subscription ID.
- resourceGroupName: The name of the resource group.
- environmentName: The name of the managed environment to create.
- containerAppName: The name of the container app to create.
- location: The Azure region for both resources (e.g. eastus).
- image: The container image to run in the app.
- targetPort: The port the container listens on for ingress traffic.
- apiVersion: Client API version.
For your developer
Arazzo workflow azure-container-apps:deploy-app-into-new-environment, 4 operations: ManagedEnvironments_CreateOrUpdate → ManagedEnvironments_Get → ContainerApps_CreateOrUpdate → ContainerApps_Get. Specs on APIs.io.