Skip to content

Commit f8b6507

Browse files
committed
initial updates to the docs per chat with ACA team
Signed-off-by: Hannah Hunter <[email protected]>
1 parent 5d42475 commit f8b6507

File tree

2 files changed

+13
-4
lines changed

2 files changed

+13
-4
lines changed

articles/container-apps/dapr-overview.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: hhunter-ms
66
ms.service: azure-container-apps
77
ms.custom: build-2023
88
ms.topic: conceptual
9-
ms.date: 01/08/2025
9+
ms.date: 04/09/2025
1010
---
1111

1212
# Microservice APIs powered by Dapr
@@ -27,6 +27,8 @@ Configure microservices APIs for your container apps environment with a [Dapr-en
2727

2828
## Versioning
2929

30+
Dapr in Azure Container Apps doesn't follow a fixed release schedule for new features. Instead, the release of new Dapr versions for new functionality depends on the prioritization and stability of the Dapr binaries. [Learn more about Dapr versions released in Azure Container Apps.](./faq.yml#how-often-are-dapr-versions-released-for-azure-container-apps-)
31+
3032
Dapr versions in Azure Container Apps include:
3133
- A semantic versioning prefix, such as `1.13.6`, which denotes compatibility with the corresponding OSS Dapr runtime version APIs and related tools like SDKs, CLI, etc.
3234
- A `-msft.<number>` suffix, which denotes incorporating Azure-specific customizations for enhanced security and production readiness.

articles/container-apps/enable-dapr.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Enable Dapr on an existing container app
3-
description: Enable Dapr on your existing Azure Container App service.
2+
title: Configure Dapr on an existing container app
3+
description: Configure Dapr on your existing Azure Container App service.
44
ms.author: hannahhunter
55
author: hhunter-ms
66
ms.service: azure-container-apps
77
ms.custom: build-2023, devx-track-bicep
88
ms.topic: conceptual
9-
ms.date: 11/25/2024
9+
ms.date: 04/08/2025
1010
---
1111

1212
# Enable Dapr on an existing container app
@@ -29,6 +29,13 @@ The following table outlines the currently supported list of Dapr sidecar config
2929
| `--dapr-read-buffer-size` | `dapr.httpReadBufferSize` | Set the max size of http header read buffer in to handle when sending multi-KB headers. The default 4 KB. |
3030
| `--dapr-api-logging` | `dapr.enableApiLogging` | Enables viewing the API calls from your application to the Dapr sidecar. |
3131
| `--dapr-log-level` | `dapr.logLevel` | Set the log level for the Dapr sidecar. Allowed values: debug, error, info, warn. Default is `info`. |
32+
| `--dapr-app-health-enabled` | `dapr.appHealth.enabled`| Enable app health checks for your container app using Boolean format. Default setting is `false`. |
33+
| `--dapr-app-health-enabled` | `dapr.appHealth.enabled`| Enable app health checks for your container app using Boolean format. Default setting is `false`. |
34+
| `--dapr-app-health-path` | `dapr.appHealth.path`| Set the path that Dapr invokes for health probes when the app channel is HTTP. This value is ignored if the app channel is using gRPC. |
35+
| `--dapr-app-health-probe-interval` | `dapr.appHealth.probeIntervalSeconds`| Number of seconds between each health probe. |
36+
| `--dapr-app-health-probe-timeout` | `dapr.appHealth.probeTimeoutMilliseconds`| Timeout in milliseconds for health probe requests. |
37+
| `--dapr-app-health-threshold` | `dapr.appHealth.threshold`| Max number of consecutive failures before the app is considered healthy. |
38+
| `--dapr-max-concurrency` | `dapr.maxConcurrency` | Limit the concurrency of your application. A valid value is any number larger than `0`. Default value is `-1`, meaning no concurrency. |
3239

3340
## Using the CLI
3441

0 commit comments

Comments
 (0)