Skip to content

Commit ae84735

Browse files
update formatting
1 parent b22353c commit ae84735

File tree

1 file changed

+17
-11
lines changed

1 file changed

+17
-11
lines changed

articles/container-apps/java-spring-cloud-config-server-usage.md

Lines changed: 17 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ The following configuration settings are available on the `spring.cloud.config.s
114114

115115
## Refresh
116116

117-
Services that consume properties need to know about the change before it happens. The default notification method for Spring Cloud Config Server involves manually triggering the refresh event, such as refresh by call `https://<YOUR-CONFIG-CLIENT-HOST-NAME>/actuator/refresh`, which may not be feasible if there are many app instances.
117+
Services that consume properties need to know about the change before it happens. The default notification method for Spring Cloud Config Server involves manually triggering the refresh event, such as refresh by call `https://<YOUR_CONFIG_CLIENT_HOST_NAME>/actuator/refresh`, which may not be feasible if there are many app instances.
118118

119119
Instead, you can automatically refresh values from Config Server by letting the config client poll for changes based on a refresh internal. Use the following steps to automatically refresh values from Config Server.
120120

@@ -189,12 +189,14 @@ By default, server-side encryption is enabled. Use the following steps to enable
189189

190190
1. Update the Spring Cloud Config Server Java component to use the git repository that has the encrypted property and set the encryption key.
191191

192+
Before you run the following command, replace placeholders surrounded by `<>` with your values.
193+
192194
```azurecli
193195
az containerapp env java-component spring-cloud-config update \
194-
--environment $ENVIRONMENT \
195-
--resource-group $RESOURCE_GROUP \
196-
--name $JAVA_COMPONENT_NAME \
197-
--configuration spring.cloud.config.server.git.uri=$URI encrypt.key=randomKey
196+
--environment <ENVIRONMENT_NAME> \
197+
--resource-group <RESOURCE_GROUP> \
198+
--name <JAVA_COMPONENT_NAME> \
199+
--configuration spring.cloud.config.server.git.uri=<URI> encrypt.key=randomKey
198200
```
199201

200202
### Client-side decryption
@@ -205,22 +207,26 @@ You can use client side decryption of properties by following the steps:
205207

206208
1. Update the Spring Cloud Config Server Java component to use the git repository that has the encrypted property and disable server-side decryption.
207209

210+
Before you run the following command, replace placeholders surrounded by `<>` with your values.
211+
208212
```azurecli
209213
az containerapp env java-component spring-cloud-config update \
210-
--environment $ENVIRONMENT \
211-
--resource-group $RESOURCE_GROUP \
212-
--name $JAVA_COMPONENT_NAME \
213-
--configuration spring.cloud.config.server.git.uri=$URI spring.cloud.config.server.encrypt.enabled=false
214+
--environment <ENVIRONMENT_NAME> \
215+
--resource-group <RESOURCE_GROUP> \
216+
--name <JAVA_COMPONENT_NAME> \
217+
--configuration spring.cloud.config.server.git.uri=<URI> spring.cloud.config.server.encrypt.enabled=false
214218
```
215219

216220
1. In your client app, add the decryption key `ENCRYPT_KEY=randomKey` as an environment variable.
217221

218222
Alternatively, if you include *spring-cloud-starter-bootstrap* on the `classpath`, or set `spring.cloud.bootstrap.enabled=true` as a system property, set `encrypt.key` in `bootstrap.properties`.
219223

224+
Before you run the following command, replace placeholders surrounded by `<>` with your values.
225+
220226
```azurecli
221227
az containerapp update \
222-
--name $APP_NAME \
223-
--resource-group $RESOURCE_GROUP \
228+
--name <APP_NAME> \
229+
--resource-group <RESOURCE_GROUP> \
224230
--set-env-vars "ENCRYPT_KEY=randomKey"
225231
```
226232

0 commit comments

Comments
 (0)