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 how to use Application Configuration Service for VMware Tanzu® with Azure Spring Apps Enterprise Tier.
20
+
This article shows you how to use Application Configuration Service for VMware Tanzu® with Azure Spring Apps Enterprise Tier.
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
@@ -28,34 +28,29 @@ With Application Configuration Service for Tanzu, you have a central place to ma
28
28
- An already provisioned Azure Spring Apps Enterprise tier instance with Application Configuration Service for Tanzu enabled. For more information, see [Quickstart: Build and deploy apps to Azure Spring Apps using the Enterprise tier](quickstart-deploy-apps-enterprise.md).
29
29
30
30
> [!NOTE]
31
-
> To use Application Configuration Service for Tanzu, you must enable it when you provision your Azure Spring Apps service instance. You can't enable the service after you provision the instance.
31
+
> To use Application Configuration Service for Tanzu, you must enable it when you provision your Azure Spring Apps service instance. You can't enable it after you provision the instance.
32
32
33
33
## Manage Application Configuration Service for Tanzu settings
34
34
35
35
Application Configuration Service for Tanzu supports Azure DevOps, GitHub, GitLab, and Bitbucket for storing your configuration files.
36
36
37
-
To manage service settings in your Azure Spring Apps instance, perform the following steps:
38
-
39
-
1. Select **Application Configuration Service** under **VMWare Tanzu components** in the navigation pane.
40
-
41
-
1. Select **Settings** and add a new entry is **Repositories**.
37
+
To manage the service settings, open the **Settings** section and add a new entry under the **Repositories** section.
42
38
43
39
:::image type="content" source="media/how-to-enterprise-application-configuration-service/config-service-settings.png" alt-text="Screenshot of the Application Configuration Service page showing how to add a repository." lightbox="media/how-to-enterprise-application-configuration-service/config-service-settings.png":::
44
40
45
41
The following table describes properties for each entry.
|**Name**| Yes | A unique name to label each Git repository. |
50
-
|**Patterns**| Yes | Patterns to search in Git repositories. For each pattern, use a format such as *{application}* or *{application}/{profile}* rather than *{application}-{profile}.yml*. Separate the patterns with commas. For more information, see the [Pattern](./how-to-enterprise-application-configuration-service.md#pattern) section of this article. |
51
-
|**URI**| Yes | A Git URI. For example: `https://github.com/Azure-Samples/piggymetrics-config` or `[email protected]:Azure-Samples/piggymetrics-config`|
52
-
|**Label**| Yes | The branch name to search in the Git repository. |
53
-
|**Search path**| No | Optional search paths, separated by commas, for searching subdirectories of the Git repository. |
54
-
|**Authentication**| Yes | Select from supported authentications. |
|`Name`| Yes | A unique name to label each Git repository. |
46
+
|`Patterns`| Yes | Patterns to search in Git repositories. For each pattern, use a format such as *{application}* or *{application}/{profile}* rather than *{application}-{profile}.yml*. Separate the patterns with commas. For more information, see the [Pattern](./how-to-enterprise-application-configuration-service.md#pattern) section of this article. |
47
+
|`URI`| Yes | A Git URI (for example, `https://github.com/Azure-Samples/piggymetrics-config` or `[email protected]:Azure-Samples/piggymetrics-config`) |
48
+
|`Label`| Yes | The branch name to search in the Git repository. |
49
+
|`Search path`| No | Optional search paths, separated by commas, for searching subdirectories of the Git repository. |
55
50
56
51
### Pattern
57
52
58
-
A configuration is pulled from Git backends by using what you define in a pattern. A pattern is a combination of *{application}/{profile}* as described in the following guidelines.
53
+
Configuration is pulled from Git backends by using what you define in a pattern. A pattern is a combination of *{application}/{profile}* as described in the following guidelines.
59
54
60
55
-*{application}* - The name of an application whose configuration you're retrieving. The value `application` is considered the default application and includes configuration information shared across multiple applications. Any other value refers to a specific application and includes properties for both the specific application and shared properties for the default application.
61
56
-*{profile}* - Optional. The name of a profile whose properties you may be retrieving. An empty value, or the value `default`, includes properties that are shared across profiles. Non-default values include properties for the specified profile and properties for the default profile.
@@ -83,15 +78,15 @@ The following image shows the three types of repository authentication supported
83
78
84
79
The following table shows the configurable properties you can use to set up a private Git repository with SSH.
|`Private key`| Yes | The private key that identifies the Git user. Passphrase-encrypted private keys aren't supported. |
89
84
|`Host key`| No | The host key of the Git server. If you've connected to the server via Git on the command line, the host key is in your *.ssh/known_hosts* file. Don't include the algorithm prefix, because it's specified in `Host key algorithm`. |
90
-
|`Host key algorithm`| No | The algorithm for `Host Key`: one of `ssh-dss`, `ssh-rsa`, `ecdsa-sha2-nistp256`, `ecdsa-sha2-nistp384`, and `ecdsa-sha2-nistp521`. Required if supplying `Host key`. |
85
+
|`Host key algorithm`| No | The algorithm for `HostKey`: one of `ssh-dss`, `ssh-rsa`, `ecdsa-sha2-nistp256`, `ecdsa-sha2-nistp384`, and `ecdsa-sha2-nistp521`. Required if supplying `Host key`. |
91
86
|`Strict host key checking`| No | Optional value that indicates whether the backend should be ignored if it encounters an error when using the provided `Host key`. Valid values are `true` and `false`. The default value is `true`. |
92
87
93
88
> [!NOTE]
94
-
> Application Configuration Service for Tanzu currently uses RSA keys with SHA-1 signatures. If you're using GitHub, for the RSA public keys added to GitHub before November 2, 2021, the corresponding private key is supported. For the RSA public keys added to GitHub after November 2, 2021, the corresponding private key is not supported and we suggest using basic authentication.
89
+
> Application Configuration Service for Tanzu uses RSA keys with SHA-1 signatures for now. If you're using GitHub, for RSA public keys added to GitHub before November 2, 2021, the corresponding private key is supported. For RSA public keys added to GitHub after November 2, 2021, the corresponding private key is not supported, and we suggest using basic authentication instead.
95
90
96
91
To validate access to the target URI, select **Validate**. After validation completes successfully, select **Apply** to update the configuration settings.
97
92
@@ -105,7 +100,7 @@ Use the following steps to refresh your application configuration after you upda
105
100
106
101
1. Load the configuration to your application.
107
102
108
-
A Spring application holds the properties as the beans of the Spring Application Context via the Environment interface. The following scenarios show different ways to load the new configurations:
103
+
A Spring application holds the properties as the beans of the Spring Application Context via the Environment interface. The following list shows several ways to load the new configurations:
109
104
110
105
- Restart the application. Restarting the application always loads the new configuration.
111
106
@@ -144,12 +139,10 @@ A Spring application holds the properties as the beans of the Spring Application
144
139
curl -X POST http://{app-endpoint}/actuator/refresh
145
140
```
146
141
147
-
## Configure Application Configuration Service for Tanzu settings
142
+
## Configure Application Configuration Service for Tanzu settings using the portal
148
143
149
144
Use the following steps to configure Application Configuration Service for Tanzu using the portal.
150
145
151
-
### [Azure portal](#tab/Portal)
152
-
153
146
1. Select **Application Configuration Service**.
154
147
1. Select **Overview** to view the running state and resources allocated to Application Configuration Service for Tanzu.
155
148
@@ -161,9 +154,10 @@ Use the following steps to configure Application Configuration Service for Tanzu
161
154
162
155
:::image type="content" source="media/how-to-enterprise-application-configuration-service/config-service-settings.png" alt-text="Screenshot of the Application Configuration Service page showing the Settings tab." lightbox="media/how-to-enterprise-application-configuration-service/config-service-settings.png":::
163
156
164
-
### [Azure CLI](#tab/Azure-CLI)
157
+
## Configure Application Configuration Service for Tanzu settings using the CLI
158
+
159
+
Use the following steps to configure Application Configuration Service for Tanzu using the CLI.
165
160
166
-
Use the following steps to configure Application Configuration Service for Tanzu.
167
161
```azurecli
168
162
az spring application-configuration-service git repo add \
169
163
--name <entry-name> \
@@ -172,12 +166,10 @@ az spring application-configuration-service git repo add \
172
166
--label <git-branch-name>
173
167
```
174
168
175
-
## Use Application Configuration Service for Tanzu with applications
169
+
## Use Application Configuration Service for Tanzu with applications using the portal
176
170
177
171
When you use Application Configuration Service for Tanzu with a Git back end and use the centralized configurations, you must bind the app to Application Configuration Service for Tanzu. After binding the app, use the following steps to configure the pattern to be used by the app.
178
172
179
-
### [Azure portal](#tab/Portal)
180
-
181
173
1. Open the **App binding** tab.
182
174
183
175
1. Select **Bind app** and choose one app in the dropdown. Select **Apply** to bind.
@@ -201,7 +193,7 @@ When you use Application Configuration Service for Tanzu with a Git back end and
201
193
202
194
1. Select **Save**
203
195
204
-
### [Azure CLI](#tab/Azure-CLI)
196
+
##Use Application Configuration Service for Tanzu with applications using the CLI
205
197
206
198
Use the following command to use Application Configuration Service for Tanzu with applications.
0 commit comments