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/how-to-enterprise-application-configuration-service.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
@@ -21,7 +21,7 @@ This article shows you how to use Application Configuration Service for VMware T
21
21
22
22
[Application Configuration Service for VMware Tanzu](https://docs.pivotal.io/tcs-k8s/0-1/) is one of the commercial VMware Tanzu components. It enables the management of Kubernetes-native `ConfigMap` resources that are populated from properties defined in one or more Git repositories.
23
23
24
-
With Application Configuration Service for Tanzu, you have a central place to manage external properties for applications across all environments. To see differences from Spring Cloud Config Server in Basic/Standard tier, you can refer to [Migrate Standard and Basic to Enterprise](./how-to-migrate-standard-tier-to-enterprise-tier.md#use-application-configuration-service-for-external-configuration).
24
+
With Application Configuration Service for Tanzu, you have a central place to manage external properties for applications across all environments. To understand the differences from Spring Cloud Config Server in Basic/Standard tier, see the [Use Application Configuration Service for external configuration](./how-to-migrate-standard-tier-to-enterprise-tier.md#use-application-configuration-service-for-external-configuration) section of [Migrate an Azure Spring Apps Basic or Standard tier instance to Enterprise tier](./how-to-migrate-standard-tier-to-enterprise-tier.md).
This article shows you how to migrate an existing application in Basic or Standard tier to Enterprise tier. When you migrate from Basic or Standard tier to Enterprise tier, VMware Tanzu components will replace the OSS Spring Cloud components to provide more feature support.
20
+
This article shows you how to migrate an existing application in Basic or Standard tier to Enterprise tier. When you migrate from Basic or Standard tier to Enterprise tier, VMware Tanzu components will replace the open-source software (OSS) Spring Cloud components to provide more feature support.
21
21
22
22
This article will use the Pet Clinic sample apps as examples of how to migrate.
23
23
@@ -132,14 +132,14 @@ The app creation steps are the same as Standard Tier.
132
132
133
133
## Use Application Configuration Service for external configuration
134
134
135
-
For externalized configuration in a distributed system, managed Spring Cloud Config Server is only available in Basic and Standard tiers. In Enterprise tier, Application Configuration Service for Tanzu (ACS) provides similar functions for your apps. Although there are some differences in usage between OSS config server and ACS.
135
+
For externalized configuration in a distributed system, managed Spring Cloud Config Server is only available in Basic and Standard tiers. In Enterprise tier, Application Configuration Service for Tanzu (ACS) provides similar functions for your apps. The following table describes some differences in usage between the OSS config server and ACS.
136
136
137
-
| Component | Support tiers |Enable | Bind to app | Profile |
| Spring Cloud Config Server | Basic/Standard | Always enabled. | Auto bound | Configured in app's source code. |
140
+
| Application Configuration Service for Tanzu | Enterprise | Enable on demand.| Manual bind | Provided as `config-file-pattern` in an Azure Spring Apps deployment.|
141
141
142
-
Unlike the client-server mode in OSS config server, ACS manages configuration by Kubernetes-native `ConfigMap` that are populated from properties defined in backend Git repositories. ACS cannot get the active profile configured in the app's source code to match the right configuration, so explicit configuration `config-file-pattern` should be specified in ASA deployment level.
142
+
Unlike the client-server mode in the OSS config server, ACS manages configuration by using the Kubernetes-native `ConfigMap`, which is populated from properties defined in backend Git repositories. ACS can't get the active profile configured in the app's source code to match the right configuration, so the explicit configuration `config-file-pattern` should be specified at the Azure Spring Apps deployment level.
143
143
144
144
## Configure Application Configuration Service for Tanzu settings
0 commit comments