You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-apps/microservices-dapr-pubsub.md
+27-12Lines changed: 27 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -152,23 +152,28 @@ cd pubsub-dapr-nodejs-servicebus
152
152
153
153
### Provision and deploy using Azure Developer CLI
154
154
155
-
1. Run `azd up` to initialize the project, provision the infrastructure, and deploy the Dapr application to Azure Container Apps in a single command.
155
+
1. Run `azd init` to initialize the project.
156
156
157
157
```azdeveloper
158
-
azd up
158
+
azd init
159
159
```
160
160
161
161
1. When prompted in the terminal, provide the following parameters.
162
162
163
163
| Parameter | Description |
164
164
| --------- | ----------- |
165
165
| Environment Name | Prefix for the resource group created to hold all Azure resources. |
166
-
| Azure Location | The Azure location for your resources. [Make sure you select a location available for Azure PostgreSQL](../postgresql/flexible-server/overview.md#azure-regions). |
166
+
| Azure Location | The Azure location for your resources. |
167
167
| Azure Subscription | The Azure subscription for your resources. |
168
168
169
+
1. Run `azd up` to provision the infrastructure and deploy the Dapr application to Azure Container Apps in a single command.
170
+
171
+
```azdeveloper
172
+
azd up
173
+
```
174
+
169
175
This process may take some time to complete. As the `azd up` command completes, the CLI output displays two Azure portal links to monitor the deployment progress. The output also demonstrates how `azd up`:
170
176
171
-
- Initializes your project using `azd init`
172
177
- Creates and configures all necessary Azure resources via the provided Bicep files in the `./infra` directory using `azd provision`. Once provisioned by Azure Developer CLI, you can access these resources via the Azure portal. The files that provision the Azure resources include:
173
178
-`main.parameters.json`
174
179
-`main.bicep`
@@ -359,23 +364,28 @@ cd pubsub-dapr-python-servicebus
359
364
360
365
### Provision and deploy using Azure Developer CLI
361
366
362
-
1. Run `azd up` to initialize the project, provision the infrastructure, and deploy the Dapr application to Azure Container Apps in a single command.
367
+
1. Run `azd init` to initialize the project.
363
368
364
369
```azdeveloper
365
-
azd up
370
+
azd init
366
371
```
367
372
368
373
1. When prompted in the terminal, provide the following parameters.
369
374
370
375
| Parameter | Description |
371
376
| --------- | ----------- |
372
377
| Environment Name | Prefix for the resource group created to hold all Azure resources. |
373
-
| Azure Location | The Azure location for your resources. [Make sure you select a location available for Azure PostgreSQL](../postgresql/flexible-server/overview.md#azure-regions). |
378
+
| Azure Location | The Azure location for your resources. |
374
379
| Azure Subscription | The Azure subscription for your resources. |
375
380
381
+
1. Run `azd up` to provision the infrastructure and deploy the Dapr application to Azure Container Apps in a single command.
382
+
383
+
```azdeveloper
384
+
azd up
385
+
```
386
+
376
387
This process may take some time to complete. As the `azd up` command completes, the CLI output displays two Azure portal links to monitor the deployment progress. The output also demonstrates how `azd up`:
377
388
378
-
- Initializes your project using `azd init`
379
389
- Creates and configures all necessary Azure resources via the provided Bicep files in the `./infra` directory using `azd provision`. Once provisioned by Azure Developer CLI, you can access these resources via the Azure portal. The files that provision the Azure resources include:
380
390
-`main.parameters.json`
381
391
-`main.bicep`
@@ -566,23 +576,28 @@ cd pubsub-dapr-csharp-servicebus
566
576
567
577
### Provision and deploy using Azure Developer CLI
568
578
569
-
1. Run `azd up` to initialize the project, provision the infrastructure, and deploy the Dapr application to Azure Container Apps in a single command.
579
+
1. Run `azd init` to initialize the project.
570
580
571
581
```azdeveloper
572
-
azd up
582
+
azd init
573
583
```
574
584
575
585
1. When prompted in the terminal, provide the following parameters.
576
586
577
587
| Parameter | Description |
578
588
| --------- | ----------- |
579
589
| Environment Name | Prefix for the resource group created to hold all Azure resources. |
580
-
| Azure Location | The Azure location for your resources. [Make sure you select a location available for Azure PostgreSQL](../postgresql/flexible-server/overview.md#azure-regions). |
590
+
| Azure Location | The Azure location for your resources. |
581
591
| Azure Subscription | The Azure subscription for your resources. |
582
592
593
+
1. Run `azd up` to provision the infrastructure and deploy the Dapr application to Azure Container Apps in a single command.
594
+
595
+
```azdeveloper
596
+
azd up
597
+
```
598
+
583
599
This process may take some time to complete. As the `azd up` command completes, the CLI output displays two Azure portal links to monitor the deployment progress. The output also demonstrates how `azd up`:
584
600
585
-
- Initializes your project using `azd init`
586
601
- Creates and configures all necessary Azure resources via the provided Bicep files in the `./infra` directory using `azd provision`. Once provisioned by Azure Developer CLI, you can access these resources via the Azure portal. The files that provision the Azure resources include:
0 commit comments