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/spring-apps/includes/quickstart-deploy-web-app/clean-up-resources.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ author: KarlErickson
3
3
ms.author: xiada
4
4
ms.service: spring-apps
5
5
ms.topic: include
6
-
ms.date: 05/24/2022
6
+
ms.date: 07/11/2023
7
7
---
8
8
9
9
<!--
@@ -15,15 +15,15 @@ For clarity of structure, a separate markdown file is used to describe how to cl
15
15
16
16
If you plan to continue working with subsequent quickstarts and tutorials, you might want to leave these resources in place. When you no longer need the resources, you can clean up unnecessary resources to avoid Azure charges.
17
17
18
-
####[Azure portal](#tab/Azure-portal)
18
+
### [Azure portal](#tab/Azure-portal)
19
19
20
20
You can delete the Azure resource group, which includes all the resources in the resource group. Use the following steps to delete the entire resource group, including the newly created service:
21
21
22
22
1. Locate your resource group in the Azure portal. On the navigation menu, select **Resource groups**, then select the name of your resource group.
23
23
24
24
1. On your resource group page, select **Delete**. Enter the name of your resource group in the text box to confirm deletion, then select **Delete**.
Use the following steps to create a new resource group.
64
+
Use the following steps to create a new resource group:
65
65
66
-
1. Use the following command to sign in to the Azure CLI.
66
+
1. Use the following command to sign in to the Azure CLI:
67
67
68
68
```azurecli
69
69
az login
70
70
```
71
71
72
-
1. Use the following command to set the default location.
72
+
1. Use the following command to set the default location:
73
73
74
74
```azurecli
75
75
az configure --defaults location=${LOCATION}
76
76
```
77
77
78
-
1. Use the following command to list all available subscriptions to determine the subscription ID to use.
78
+
1. Use the following command to list all available subscriptions to determine the subscription ID to use:
79
79
80
80
```azurecli
81
81
az account list --output table
@@ -87,13 +87,13 @@ Use the following steps to create a new resource group.
87
87
az account set --subscription <subscription-ID>
88
88
```
89
89
90
-
1. Use the following command to create a resource group.
90
+
1. Use the following command to create a resource group:
91
91
92
92
```azurecli
93
93
az group create --resource-group ${RESOURCE_GROUP}
94
94
```
95
95
96
-
1. Use the following command to set the newly created resource group as the default resource group.
96
+
1. Use the following command to set the newly created resource group as the default resource group:
97
97
98
98
```azurecli
99
99
az configure --defaults group=${RESOURCE_GROUP}
@@ -159,7 +159,7 @@ Specifying `0.0.0.0` enables public access from any resources deployed within Az
159
159
160
160
### 3.5. Connect app instance to PostgreSQL instance
161
161
162
-
After the application instance and the PostgreSQL instance are created, the application instance can't access the PostgreSQL instance directly. Use the following steps to enable the app to connect to the PostgreSQL instance.
162
+
After the application instance and the PostgreSQL instance are created, the application instance can't access the PostgreSQL instance directly. Use the following steps to enable the app to connect to the PostgreSQL instance:
163
163
164
164
1. Use the following command to get the PostgreSQL instance's fully qualified domain name:
165
165
@@ -183,13 +183,11 @@ After the application instance and the PostgreSQL instance are created, the appl
183
183
184
184
## 4. Deploy the app to Azure Spring Apps
185
185
186
-
Now that the cloud environment is prepared, the application is ready to deploy.
186
+
Now that the cloud environment is prepared, the application is ready to deploy. Use the following command to deploy the app:
0 commit comments