Skip to content

Commit abb88fc

Browse files
authored
Merge pull request #197033 from craigshoemaker/aca/method
[Container Apps] Update Dapr URL pattern
2 parents 432d779 + 25e6dfc commit abb88fc

File tree

2 files changed

+7
-2
lines changed

2 files changed

+7
-2
lines changed

articles/container-apps/connect-apps.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,8 @@ services: container-apps
55
author: craigshoemaker
66
ms.service: container-apps
77
ms.topic: conceptual
8-
ms.date: 11/02/2021
8+
ms.date: 04/04/2022
99
ms.author: cshoe
10-
ms.custom: ignite-fall-2021
1110
---
1211

1312
# Connect applications in Azure Container Apps Preview
@@ -21,6 +20,8 @@ Once you know a container app's domain name, then you can call the location with
2120
2221
A sample solution showing how you can call between containers using both the FQDN Location or Dapr can be found on [Azure Samples](https://github.com/Azure-Samples/container-apps-connect-multiple-apps)
2322

23+
For more details about connecting Dapr applications, refer to [Invoke services using HTTP](https://docs.dapr.io/developing-applications/building-blocks/service-invocation/howto-invoke-discover-services/).
24+
2425
## Location
2526

2627
A container app's location is composed of values associated with its environment, name, and region. Available through the `azurecontainerapps.io` top-level domain, the fully qualified domain name (FQDN) uses:
@@ -41,6 +42,10 @@ Developing microservices often requires you to implement patterns common to dist
4142

4243
A microservice that uses Dapr is available through the following URL pattern:
4344

45+
```text
46+
http://localhost:3500/v1.0/invoke/<YOUR_APP_NAME>/method
47+
```
48+
4449
:::image type="content" source="media/connect-apps/azure-container-apps-location-dapr.png" alt-text="Azure Container Apps container app location with Dapr.":::
4550

4651
## Next steps
0 Bytes
Loading

0 commit comments

Comments
 (0)