Enable Dapr Sidecar
A 4-step recipe with Azure Container Apps. We can help you get access.
Recipe · 4 steps
Enable Dapr Sidecar
with Azure Container Apps · IT Infrastructure Management
Turn on the Dapr sidecar for an app and confirm the new revision rolls out.
- Read the container app to confirm it exists before enabling the Dapr sidecar on its configuration.
- Patch the container app configuration to enable the Dapr sidecar with the supplied app id, protocol, and port in the ARM properties envelope.
- Read the container app and check its provisioningState, looping while the Dapr change is still rolling out and proceeding once it settles.
- List the app's revisions to expose the Dapr-enabled revision.
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).
- daprAppId: The Dapr application identifier for the sidecar.
- daprAppPort: The port Dapr uses to communicate with the app.
- apiVersion: Client API version.
For your developer
Arazzo workflow azure-container-apps:enable-dapr-sidecar, 4 operations: ContainerApps_Get → ContainerApps_Update → ContainerApps_Get → ContainerAppsRevisions_ListRevisions. Specs on APIs.io.