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
This article shows you how to use Application Configuration Service with Azure Spring Cloud Enterprise Tier.
17
+
This article shows you how to use Application Configuration Service for VMware Tanzu® with Azure Spring Cloud Enterprise Tier.
18
18
19
-
[Application Configuration Service](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.
19
+
[Application Configuration Service for 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.
20
20
21
-
With Application Configuration Service, you have a central place to manage external properties for applications across all environments.
21
+
With Application Configuration Service for Tanzu, you have a central place to manage external properties for applications across all environments.
22
22
23
23
## Prerequisites
24
24
25
-
- An already provisioned Azure Spring Cloud Enterprise tier instance with Application Configuration Service enabled. For more information, see [Quickstart: Provision an Azure Spring Cloud service instance using the Enterprise tier](quickstart-provision-service-instance-enterprise.md).
25
+
- An already provisioned Azure Spring Cloud Enterprise tier instance with Application Configuration Service for Tanzu enabled. For more information, see [Quickstart: Provision an Azure Spring Cloud service instance using the Enterprise tier](quickstart-provision-service-instance-enterprise.md).
26
26
27
27
> [!NOTE]
28
-
> To use Application Configuration Service, you must enable it when you provision your Azure Spring Cloud service instance. You cannot enable it after provisioning at this time.
28
+
> To use Application Configuration Service for Tanzu, you must enable it when you provision your Azure Spring Cloud service instance. You cannot enable it after provisioning at this time.
29
29
30
-
## Manage Application Configuration Service settings
30
+
## Manage Application Configuration Service for Tanzu settings
31
31
32
-
Application Configuration Service supports Azure DevOps, GitHub, GitLab, and Bitbucket for storing your configuration files.
32
+
Application Configuration Service for Tanzu supports Azure DevOps, GitHub, GitLab, and Bitbucket for storing your configuration files.
33
33
34
34
To manage the service settings, open the **Settings** section and add a new entry under the **Repositories** section.
35
35
@@ -54,7 +54,7 @@ Configuration will be pulled from Git backends using what is defined in a patter
54
54
55
55
### Authentication
56
56
57
-
The following image shows the three types of repository authentication supported by Application Configuration Service.
57
+
The following image shows the three types of repository authentication supported by Application Configuration Service for Tanzu.
58
58
59
59
:::image type="content" source="media/enterprise/how-to-enterprise-application-configuration-service/config-service-auth.png" alt-text="Screenshot of where to edit authentication types.":::
60
60
@@ -88,7 +88,7 @@ To validate access to the target URI, select **Validate**. After validation comp
88
88
89
89
Use the following steps to refresh your application configuration after you update the configuration file in the Git repository.
90
90
91
-
1. Load the configuration to Application Configuration Service.
91
+
1. Load the configuration to Application Configuration Service for Tanzu.
92
92
93
93
The refresh frequency is managed by Azure Spring Cloud and fixed to 60 seconds.
94
94
@@ -133,12 +133,12 @@ A Spring application holds the properties as the beans of the Spring Application
133
133
curl -X POST http://{app-endpoint}/actuator/refresh
134
134
```
135
135
136
-
## Configure Application Configuration Service settings using the portal
136
+
## Configure Application Configuration Service for Tanzu settings using the portal
137
137
138
-
You can configure Application Configuration Service using the portal by following these steps:
138
+
You can configure Application Configuration Service for Tanzu using the portal by following these steps:
139
139
140
140
1. Select **Application Configuration Service**.
141
-
1. Select **Overview** to view the running state and resources allocated to Application Configuration Service.
141
+
1. Select **Overview** to view the running state and resources allocated to Application Configuration Service for Tanzu.
142
142
143
143
144
144
@@ -148,9 +148,9 @@ You can configure Application Configuration Service using the portal by followin
148
148
149
149
150
150
151
-
## Configure Application Configuration Service settings using the CLI
151
+
## Configure Application Configuration Service for Tanzu settings using the CLI
152
152
153
-
You can configure Application Configuration Service using the CLI, by following these steps:
153
+
You can configure Application Configuration Service for Tanzu using the CLI, by following these steps:
154
154
155
155
```azurecli
156
156
az spring-cloud application-configuration-service git repo add \
## Use Application Configuration Service with applications using the portal
163
+
## Use Application Configuration Service for Tanzu with applications using the portal
164
164
165
-
When you use Application Configuration Service with a Git back end, keep the following items in mind.
165
+
When you use Application Configuration Service for Tanzu with a Git back end, keep the following items in mind.
166
166
167
-
To use the centralized configurations, you must bind the app to Application Configuration Service. After binding the app, you'll need to configure which pattern to be used by the app by following these steps:
167
+
To use the centralized configurations, you must bind the app to Application Configuration Service for Tanzu. After binding the app, you'll need to configure which pattern to be used by the app by following these steps:
168
168
169
169
1. Open the **App binding** tab.
170
170
@@ -185,13 +185,13 @@ To use the centralized configurations, you must bind the app to Application Conf
185
185
186
186
d. In the **Config file patterns** dropdown, choose one or more patterns from the list.
187
187
188
-
:::image type="content" source="media/enterprise/how-to-enterprise-application-configuration-service/config-service-pattern.png" alt-text="Screenshot of the pattern selection screen.":::
188
+
:::image type="content" source="media/enterprise/how-to-enterprise-application-configuration-service/config-service-pattern.png" alt-text="Screenshot of the pattern selection screen.":::
189
189
190
190
e. Select **Save**
191
191
192
-
## Use Application Configuration Service with applications using the CLI
192
+
## Use Application Configuration Service for Tanzu with applications using the CLI
193
193
194
-
You can use Application Configuration Service with applications, by using this command:
194
+
You can use Application Configuration Service for Tanzu with applications, by using this command:
195
195
196
196
```azurecli
197
197
az spring-cloud application-configuration-service bind --app <app-name>
This article describes the extra configuration and functionality included in Build Service with Azure Spring Cloud Enterprise Tier.
17
+
This article describes the extra configuration and functionality included in VMware Tanzu® Build Service™ with Azure Spring Cloud Enterprise Tier.
18
18
19
19
In Azure Spring Cloud, the existing Standard tier already supports compiling user source code into [OCI images](https://opencontainers.org/) through [Kpack](https://github.com/pivotal/kpack). Kpack is a Kubernetes (K8s) implementation of [Cloud Native Buildpacks (CNB)](https://buildpacks.io/) provided by VMware. This article provides details about the extra configurations and functionality exposed in the Azure Spring Cloud Enterprise tier.
20
20
21
21
## Build Agent Pool
22
22
23
-
Build Service in the Enterprise tier is the entry point to containerize user applications from both source code and artifacts. There's a dedicated build agent pool that reserves compute resources for a given number of concurrent build tasks. The build agent pool prevents resource contention with your running apps. You can configure the number of resources given to the build agent pool during or after creating a new service instance of Azure Spring Cloud using the **VMware Tanzu settings**.
23
+
Tanzu Build Service in the Enterprise tier is the entry point to containerize user applications from both source code and artifacts. There's a dedicated build agent pool that reserves compute resources for a given number of concurrent build tasks. The build agent pool prevents resource contention with your running apps. You can configure the number of resources given to the build agent pool during or after creating a new service instance of Azure Spring Cloud using the **VMware Tanzu settings**.
24
24
25
25
:::image type="content" source="media/enterprise/how-to-enterprise-build-service/agent-pool.png" alt-text="Azure portal screenshot showing Azure Spring Cloud Create page with 'VMWare Tanzu settings' highlighted and 'Allocated Resources' dropdown showing.":::
26
26
@@ -34,13 +34,13 @@ The Build Agent Pool scale set sizes available are:
34
34
| S4 | 5 vCPU, 10 Gi |
35
35
| S5 | 6 vCPU, 12 Gi |
36
36
37
-
The following image shows the resources given to the Build Service Agent Pool after you've successfully provisioned the service instance.
37
+
The following image shows the resources given to the Tanzu Build Service Agent Pool after you've successfully provisioned the service instance.
38
38
39
39
:::image type="content" source="media/enterprise/how-to-enterprise-build-service/agent-pool-size.png" alt-text="Azure portal screenshot showing Azure Spring Cloud Build Service page with 'General info' highlighted.":::
40
40
41
41
## Default Builder and Tanzu Buildpacks
42
42
43
-
In the Enterprise Tier, a default builder is provided within Build Service with a list of commercial Tanzu Buildpacks.
43
+
In the Enterprise Tier, a default builder is provided within Tanzu Build Service with a list of commercial VMware Tanzu® Buildpacks.
44
44
45
45
Tanzu Buildpacks make it easier to integrate with other software like New Relic. They're configured as optional and will only run with proper configuration. For more information, see the [Buildpack bindings](#buildpack-bindings) section.
46
46
@@ -52,7 +52,7 @@ The following list shows the Tanzu Buildpacks available in Azure Spring Cloud En
52
52
- tanzu-buildpacks/nodejs
53
53
- tanzu-buildpacks/python
54
54
55
-
For details about buildpacks, see [Using the Tanzu Partner Buildpacks](https://docs.pivotal.io/tanzu-buildpacks/partner-integrations/partner-integration-buildpacks.html).
55
+
For details about Tanzu Buildpacks, see [Using the Tanzu Partner Buildpacks](https://docs.pivotal.io/tanzu-buildpacks/partner-integrations/partner-integration-buildpacks.html).
This article shows you how to view the Azure Spring Cloud Enterprise Tier with VMware Tanzu offering through Azure Marketplace and how to redirect to the Azure Spring Cloud Enterprise tier creation page from Azure Marketplace.
17
17
18
-
Azure Spring Cloud Enterprise Tier is optimized for the needs of enterprise Spring developers through advanced configurability, flexibility, portability, and enterprise-ready VMware Spring Runtime 24x7 support. Developers also benefit from commercial Tanzu components, such as Tanzu Build Service, Tanzu Application Configuration Service, and Tanzu Service Registry, and access to Spring experts.
18
+
Azure Spring Cloud Enterprise Tier is optimized for the needs of enterprise Spring developers through advanced configurability, flexibility, portability, and enterprise-ready VMware Spring Runtime 24x7 support. Developers also benefit from commercial Tanzu components, such as VMware Tanzu® Build Service™, Application Configuration Service for VMware Tanzu®, and VMware Tanzu® Service Registry, and access to Spring experts.
19
19
20
20
You can obtain and pay for a license to Tanzu components through an [Azure Marketplace offering](https://aka.ms/ascmpoffer). Azure Spring Cloud manages the license acquisition so you won't have to do it yourself.
21
21
@@ -31,7 +31,7 @@ To purchase in the Azure Marketplace, you must meet the following prerequisites:
31
31
32
32
## View Azure Spring Cloud Enterprise Tier with VMware Tanzu offering from Azure Marketplace
33
33
34
-
To see the offering and read a detailed description, see [Azure Spring Cloud Enterprise Tier w/VMware Tanzu](https://aka.ms/ascmpoffer).
34
+
To see the offering and read a detailed description, see [Azure Spring Cloud Enterprise Tier](https://aka.ms/ascmpoffer).
35
35
36
36
To see the supported plans in your market, select **Plans + Pricing**.
This article shows you how to use Service Registry with Azure Spring Cloud Enterprise Tier.
17
+
This article shows you how to use VMware Tanzu® Service Registry with Azure Spring Cloud Enterprise Tier.
18
18
19
-
[Service Registry](https://docs.vmware.com/en/Spring-Cloud-Services-for-VMware-Tanzu/2.1/spring-cloud-services/GUID-service-registry-index.html) is one of the commercial VMware Tanzu components. It provides your apps with an implementation of the Service Discovery pattern, one of the key tenets of a Spring-based architecture. It can be difficult, and brittle in production, to hand-configure each client of a service or adopt some form of access convention. Instead, your apps can use the Service Registry to dynamically discover and call registered services.
19
+
[Tanzu Service Registry](https://docs.vmware.com/en/Spring-Cloud-Services-for-VMware-Tanzu/2.1/spring-cloud-services/GUID-service-registry-index.html) is one of the commercial VMware Tanzu components. It provides your apps with an implementation of the Service Discovery pattern, one of the key tenets of a Spring-based architecture. It can be difficult, and brittle in production, to hand-configure each client of a service or adopt some form of access convention. Instead, your apps can use Tanzu Service Registry to dynamically discover and call registered services.
20
20
21
21
## Prerequisites
22
22
23
-
- An already provisioned Azure Spring Cloud Enterprise tier instance with Service Registry enabled. For more information, see [Quickstart: Provision an Azure Spring Cloud service instance using the Enterprise tier](quickstart-provision-service-instance-enterprise.md).
23
+
- An already provisioned Azure Spring Cloud Enterprise tier instance with Tanzu Service Registry enabled. For more information, see [Quickstart: Provision an Azure Spring Cloud service instance using the Enterprise tier](quickstart-provision-service-instance-enterprise.md).
24
24
25
25
> [!NOTE]
26
-
> To use Service Registry, you must enable it when you provision your Azure Spring Cloud service instance. You cannot enable it after provisioning at this time.
26
+
> To use Tanzu Service Registry, you must enable it when you provision your Azure Spring Cloud service instance. You cannot enable it after provisioning at this time.
27
27
28
28
## Use Service Registry with apps
29
29
30
-
Before your application can manage service registration and discovery using Service Registry, you must include the following dependency in your application's *pom.xml* file:
30
+
Before your application can manage service registration and discovery using Tanzu Service Registry, you must include the following dependency in your application's *pom.xml* file:
31
31
32
32
```xml
33
33
<dependency>
@@ -48,7 +48,7 @@ public class DemoApplication {
48
48
}
49
49
```
50
50
51
-
Use the following steps to bind an application to the Service Registry.
51
+
Use the following steps to bind an application to Tanzu Service Registry.
0 commit comments