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-cloud/overview.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -126,7 +126,6 @@ The following quickstarts will help you get started using the Enterprise tier:
126
126
*[Provision an Azure Spring Cloud instance using the Enterprise tier](quickstart-provision-service-instance-enterprise.md)
127
127
*[Set up Application Configuration Service for Tanzu](quickstart-setup-application-configuration-service-enterprise.md)
128
128
*[Build and deploy applications](quickstart-deploy-apps-enterprise.md)
129
-
*[Set up Tanzu Service Registry](quickstart-setup-service-registry-enterprise.md)
130
129
131
130
Most of the Azure Spring Cloud documentation applies to all tiers. Some articles apply only to Enterprise tier or only to Basic/Standard tier, as indicated at the beginning of each article.
Copy file name to clipboardExpand all lines: articles/spring-cloud/quickstart-deploy-apps-enterprise.md
+49-9Lines changed: 49 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,47 @@ To create apps on Azure Spring Cloud, follow these steps:
41
41
az spring-cloud app create --name customers-service --instance-count 1 --memory 2Gi
42
42
```
43
43
44
+
## Bind apps to Application Configuration Service for Tanzu and Tanzu Service Registry
45
+
46
+
### [Portal](#tab/azure-portal)
47
+
48
+
To bind apps to Application Configuration Service for VMware Tanzu®, follow these steps.
49
+
50
+
1. In the Azure portal, select **Application Configuration Service**.
51
+
1. Select **App binding**, then select **Bind app**.
52
+
1. Choose one app in the dropdown and select **Apply** to bind the application to Application Configuration Service for Tanzu.
53
+
54
+

55
+
56
+
A list under **App name** shows the apps bound with Application Configuration Service for Tanzu, as shown in the following screenshot:
57
+
58
+

59
+
60
+
To bind apps to VMware Tanzu® Service Registry, follow these steps.
61
+
62
+
1. Select **Service Registry**.
63
+
1. Select **App binding**, then select **Bind app**.
64
+
1. Choose one app in the dropdown, and then select **Apply** to bind the application to Tanzu Service Registry.
65
+
66
+
:::image type="content" source="media/enterprise/getting-started-enterprise/service-reg-app-bind-dropdown.png" alt-text="Azure portal screenshot of Azure Spring Cloud with Service Registry page and 'Bind app' dialog showing.":::
67
+
68
+
A list under **App name** shows the apps bound with Tanzu Service Registry, as shown in the following screenshot:
69
+
70
+
:::image type="content" source="media/enterprise/getting-started-enterprise/service-reg-app-bind.png" alt-text="Azure portal screenshot of Azure Spring Cloud with Service Registry page and 'App binding' section showing.":::
71
+
72
+
### [Azure CLI](#tab/azure-cli)
73
+
74
+
To bind apps to Application Configuration Service for VMware Tanzu® and VMware Tanzu® Service Registry, use the following commands.
75
+
76
+
```azurecli
77
+
az spring-cloud application-configuration-service bind --app api-gateway
78
+
az spring-cloud application-configuration-service bind --app customers-service
79
+
az spring-cloud service-registry bind --app api-gateway
80
+
az spring-cloud service-registry bind --app customers-service
81
+
```
82
+
83
+
---
84
+
44
85
## Build and deploy applications
45
86
46
87
The following sections show how to build and deploy applications.
@@ -95,17 +136,16 @@ Access the `api gateway` and `customers service` applications from the browser u
95
136
96
137
## Clean up resources
97
138
98
-
1. Open the [Azure portal](https://ms.portal.azure.com/?AppPlatformExtension=entdf#home), then delete the service instance as in the following screenshot.
99
-
100
-

101
-
102
-
1. Run the following command to remove the preview version of the Azure CLI extension.
139
+
If you plan to continue working with subsequent quickstarts and tutorials, you might want to leave these resources in place. When no longer needed, delete the resource group, which deletes the resources in the resource group. To delete the resource group by using Azure CLI, use the following commands:
103
140
104
-
```azurecli
105
-
az extension remove --name spring-cloud
106
-
```
141
+
```azurecli
142
+
echo "Enter the Resource Group name:" &&
143
+
read resourceGroupName &&
144
+
az group delete --name $resourceGroupName &&
145
+
echo "Press [ENTER] to continue ..."
146
+
```
107
147
108
148
## Next steps
109
149
110
150
> [!div class="nextstepaction"]
111
-
> [Quickstart: Set up Tanzu Service Registry](quickstart-setup-service-registry-enterprise.md)
151
+
> [Quickstart: Set up a Log Analytics workspace](quickstart-setup-log-analytics.md)
Copy file name to clipboardExpand all lines: articles/spring-cloud/quickstart-deploy-apps.md
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -415,9 +415,18 @@ Other Spring applications included in this sample can be deployed similarly.
415
415
416
416
::: zone-end
417
417
418
-
## Next steps
418
+
## Clean up resources
419
+
420
+
If you plan to continue working with subsequent quickstarts and tutorials, you might want to leave these resources in place. When no longer needed, delete the resource group, which deletes the resources in the resource group. To delete the resource group by using Azure CLI, use the following commands:
421
+
422
+
```azurecli
423
+
echo "Enter the Resource Group name:" &&
424
+
read resourceGroupName &&
425
+
az group delete --name $resourceGroupName &&
426
+
echo "Press [ENTER] to continue ..."
427
+
```
419
428
420
-
In this quickstart, you created Azure resources that will continue to accrue charges if they remain in your subscription. If you don't intend to continue on to the next quickstart, see [Clean up resources](./quickstart-logs-metrics-tracing.md#clean-up-resources). Otherwise, advance to the next quickstart:
429
+
## Next steps
421
430
422
431
> [!div class="nextstepaction"]
423
-
> [Set up Log Analytics](./quickstart-setup-log-analytics.md)
432
+
> [Quickstart: Set up a Log Analytics workspace](quickstart-setup-log-analytics.md)
Copy file name to clipboardExpand all lines: articles/spring-cloud/quickstart-deploy-infrastructure-vnet-bicep.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -154,7 +154,7 @@ You can either use the Azure portal to check the deployed resources, or use Azur
154
154
155
155
If you plan to continue working with subsequent quickstarts and tutorials, you might want to leave these resources in place. When no longer needed, delete the resource group, which deletes the resources in the resource group. To delete the resource group by using Azure CLI, use the following commands:
Copy file name to clipboardExpand all lines: articles/spring-cloud/quickstart-integrate-azure-database-mysql.md
+89-70Lines changed: 89 additions & 70 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,8 +17,7 @@ Pet Clinic, as deployed in the default configuration [Quickstart: Build and depl
17
17
18
18
## Variables preparation
19
19
20
-
We will use the following values. Save them in a text file or environment variables to avoid errors.
21
-
The password should be at least 8 characters long and contain at least one English uppercase letter, one English lowercase letter, one number, and one non-alphanumeric character (!, $, #, %, and so on.).
20
+
We will use the following values. Save them in a text file or environment variables to avoid errors. The password should be at least 8 characters long and contain at least one English uppercase letter, one English lowercase letter, one number, and one non-alphanumeric character (!, $, #, %, and so on.).
22
21
23
22
```bash
24
23
export RESOURCE_GROUP=<resource-group-name># customize this
To enable MySQL as database for the sample app, simply update the *customer-service* app with active profile MySQL and database credentials as environment variables.
128
131
129
132
```azcli
130
-
az spring-cloud app update --name customers-service \
If you plan to continue working with subsequent quickstarts and tutorials, you might want to leave these resources in place. When no longer needed, delete the resource group, which deletes the resources in the resource group. To delete the resource group by using Azure CLI, use the following commands:
176
+
177
+
```azurecli
178
+
echo "Enter the Resource Group name:" &&
179
+
read resourceGroupName &&
180
+
az group delete --name $resourceGroupName &&
181
+
echo "Press [ENTER] to continue ..."
182
+
```
183
+
165
184
## Next steps
166
185
167
186
*[Bind an Azure Database for MySQL instance to your application in Azure Spring Cloud](how-to-bind-mysql.md)
Copy file name to clipboardExpand all lines: articles/spring-cloud/quickstart-logs-metrics-tracing.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -232,10 +232,13 @@ Select an exception to see the end-to-end transaction and stacktrace in context:
232
232
233
233
## Clean up resources
234
234
235
-
In these quickstarts, you created Azure resources that will continue to accrue charges if they remain in your subscription. If you don't expect to need these resources in the future, delete the resource group by using the portal or by running the following command in the Cloud Shell:
235
+
If you plan to continue working with subsequent quickstarts and tutorials, you might want to leave these resources in place. When no longer needed, delete the resource group, which deletes the resources in the resource group. To delete the resource group by using Azure CLI, use the following commands:
236
236
237
237
```azurecli
238
-
az group delete --name <your resource group name; for example: helloworld-1558400876966-rg> --yes
238
+
echo "Enter the Resource Group name:" &&
239
+
read resourceGroupName &&
240
+
az group delete --name $resourceGroupName &&
241
+
echo "Press [ENTER] to continue ..."
239
242
```
240
243
241
244
In an earlier quickstart, you also set the default resource group name. If you don't intend to continue to the next quickstart, clear out that default by running the following CLI command:
@@ -249,8 +252,5 @@ az config set defaults.group=
249
252
To explore more monitoring capabilities of Azure Spring Cloud, see:
0 commit comments