Skip to content

Commit 14f3808

Browse files
committed
add section for service creation with config server enable
1 parent e682246 commit 14f3808

File tree

5 files changed

+82
-3
lines changed

5 files changed

+82
-3
lines changed

articles/spring-apps/enterprise/how-to-enterprise-config-server.md

Lines changed: 82 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,80 @@ Spring Cloud Config Server provides server and client-side support for an extern
4848

4949
- [Git](https://git-scm.com/downloads).
5050

51+
::: zone pivot="sc-enterprise"
52+
53+
## Enable Spring Cloud Config Server
54+
55+
You can enable Spring Cloud Config Server when you provision an Azure Spring Apps Enterprise plan instance. If you already have an Azure Spring Apps Enterprise plan resource, see the [Manage Spring Cloud Config Server in an existing Enterprise plan instance](#manage-spring-cloud-config-in-an-existing-enterprise-plan-instance) section to enable it.
56+
57+
You can enable Spring Cloud Config Server using the Azure portal or Azure CLI.
58+
59+
### [Azure portal](#tab/Portal)
60+
61+
Use the following steps to enable Spring Cloud Config Server using the Azure portal:
62+
63+
1. Open the [Azure portal](https://portal.azure.com).
64+
65+
1. On the **Basics** tab, select **Enterprise tier** in the **Pricing** section and specify the required information. Then select **Next: Managed components**.
66+
67+
1. On the **Managed components** tab, select **Enable Spring Cloud Config Server (preview)**.
68+
69+
:::image type="content" source="media/how-to-enterprise-config-server/create-instance.png" alt-text="Screenshot of the Azure portal that shows the VMware Tanzu settings tab with the Enable Spring Cloud Config Server checkbox highlighted." lightbox="media/how-to-enterprise-config-server/create-instance.png":::
70+
71+
1. Specify other settings, and then select **Review and Create**.
72+
73+
1. On the **Review an create** tab, make sure that **Enable Spring Cloud Config Server (preview)** is set to **Yes**. Select **Create** to create the Enterprise plan instance.
74+
75+
### [Azure CLI](#tab/Azure-CLI)
76+
77+
Use the following steps to provision an Azure Spring Apps service instance with Spring Cloud Config Server enabled using the Azure CLI.
78+
79+
1. Use the following command to sign in to the Azure CLI and choose your active subscription:
80+
81+
```azurecli
82+
az login
83+
az account list --output table
84+
az account set --subscription <subscription-ID>
85+
```
86+
87+
1. Use the following command to accept the legal terms and privacy statements for the Azure Spring Apps Enterprise plan. This step is necessary only if your subscription has never been used to create an Enterprise plan instance.
88+
89+
```azurecli
90+
az provider register --namespace Microsoft.SaaS
91+
az term accept \
92+
--publisher vmware-inc \
93+
--product azure-spring-cloud-vmware-tanzu-2 \
94+
--plan asa-ent-hr-mtr
95+
```
96+
97+
1. Select a location. The location must support the Azure Spring Apps Enterprise plan. For more information, see the [Azure Spring Apps FAQ](faq.md).
98+
99+
1. Use the following command to create a resource group:
100+
101+
```azurecli
102+
az group create \
103+
--name <resource-group-name> \
104+
--location <location>
105+
```
106+
107+
For more information about resource groups, see [What is Azure Resource Manager?](../../azure-resource-manager/management/overview.md)
108+
109+
1. Prepare a name for your Azure Spring Apps service instance. The name must be between 4 and 32 characters long and can contain only lowercase letters, numbers, and hyphens. The first character of the service name must be a letter and the last character must be either a letter or a number.
110+
111+
1. Use the following command to create an Azure Spring Apps service instance with Spring Cloud Config Server enabled:
112+
113+
```azurecli
114+
az spring create \
115+
--resource-group <resource-group-name> \
116+
--name <Azure-Spring-Apps-service-instance-name> \
117+
--sku enterprise \
118+
--enable-config-server
119+
```
120+
121+
---
122+
123+
::: zone-end
124+
51125
## Restriction
52126

53127
There are some restrictions when you use Config Server with a Git back end. The following properties are automatically injected into your application environment to access Config Server and Service Discovery. If you also configure those properties from your Config Server files, you might experience conflicts and unexpected behavior.
@@ -333,7 +407,7 @@ az spring config-server bind \
333407

334408
You can also set up the app binding from the Azure portal, as shown in the following screenshot:
335409

336-
:::image type="content" source="./media/how-to-enterprise-config-server/spring-cloud-config-server-bind-app.png" alt-text="Screenshot of the Azure portal that shows the Spring Cloud Config Server page with the App binding dropdown highlighted.":::
410+
:::image type="content" source="media/how-to-enterprise-config-server/spring-cloud-config-server-bind-app.png" lightbox="media/how-to-enterprise-config-server/spring-cloud-config-server-bind-app.png" alt-text="Screenshot of the Azure portal that shows the Spring Cloud Config Server page with the App binding dropdown highlighted.":::
337411

338412
> [!NOTE]
339413
> These changes will take a few minutes to propagate to all applications when the config server status changes.
@@ -352,7 +426,7 @@ az spring app create \
352426

353427
You can also bind your application to the Spring Cloud Config Server from the Azure portal, as shown in the following screenshot:
354428

355-
:::image type="content" source="media/how-to-enterprise-config-server/spring-cloud-config-server-bind-app-when-creation.png" alt-text="Screenshot of the Azure portal that shows the Create App page with the Bind dropdown highlighted.":::
429+
:::image type="content" source="media/how-to-enterprise-config-server/spring-cloud-config-server-bind-app-when-creation.png" lightbox="media/how-to-enterprise-config-server/spring-cloud-config-server-bind-app-when-creation.png" alt-text="Screenshot of the Azure portal that shows the Create App page with the Bind dropdown highlighted.":::
356430

357431
::: zone-end
358432

@@ -426,7 +500,7 @@ For more information, see the [config-client-polling](https://github.com/Azure-S
426500

427501
::: zone pivot="sc-enterprise"
428502

429-
## Enable/disable Spring Cloud Config Server after service creation
503+
## Manage Spring Cloud Config Server in an existing Enterprise plan instance
430504

431505
You can enable and disable Spring Cloud Config Server after service creation using the Azure portal or Azure CLI. Before disabling Spring Cloud Config Server, you're required to unbind all of your apps from it.
432506

@@ -435,8 +509,13 @@ You can enable and disable Spring Cloud Config Server after service creation usi
435509
Use the following steps to enable or disable Spring Cloud Config Server using the Azure portal:
436510

437511
1. Navigate to your service resource, and then select **Spring Cloud Config Server**.
512+
438513
1. Select **Manage**.
514+
439515
1. Select or unselect the **Enable Spring Cloud Config Server**, and then select **Save**.
516+
517+
:::image type="content" source="media/how-to-enterprise-config-server/enable-config-server.png" alt-text="Screenshot of the Azure portal that shows the Manage pane with the Enable Config Server option highlighted." lightbox="media/how-to-enterprise-config-server/enable-config-server.png":::
518+
440519
1. You can now view the state of Spring Cloud Config Server on the **Spring Cloud Config Server** page.
441520

442521
### [Azure CLI](#tab/Azure-CLI)
263 KB
Loading
61.9 KB
Loading
Loading
168 KB
Loading

0 commit comments

Comments
 (0)