Skip to content

Commit 5ee0ab9

Browse files
KarlEricksonKarlErickson
committed
edits, image resize/compression
1 parent 5d0600f commit 5ee0ab9

File tree

2 files changed

+12
-8
lines changed

2 files changed

+12
-8
lines changed

‎articles/spring-apps/enterprise/how-to-enterprise-application-configuration-service.md

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -68,9 +68,9 @@ The following table describes the properties for each repository entry:
6868
| Property | Required? | Description |
6969
|---------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
7070
| `Name` | Yes | A unique name to label each Git repository. |
71-
| `Patterns` | Yes | The pattern type 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](#pattern) section of this article. |
71+
| `Patterns` | Yes | The patterns to search for 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](#pattern) section of this article. |
7272
| `URI` | Yes | A Git URI (for example, `https://github.com/Azure-Samples/piggymetrics-config` or `[email protected]:Azure-Samples/piggymetrics-config`) |
73-
| `Label` | Yes | The branch name to search in the Git repository. |
73+
| `Label` | Yes | The branch name to search for in the Git repository. |
7474
| `Search path` | No | Optional search paths, separated by commas, for searching subdirectories of the Git repository. |
7575

7676
### Pattern
@@ -155,7 +155,7 @@ The Application Configuration Service also supports polyglot apps like dotNET, G
155155
When you modify and commit your configurations in a Git repository, several steps are involved before these changes are reflected in your applications. This process, though automated, involves the following distinct stages and components, each with its own timing and behavior:
156156

157157
- Polling by Application Configuration Service: The Application Configuration Service regularly polls the backend Git repositories to detect any changes. This polling occurs at a set frequency, defined by the refresh interval. When a change is detected, Application Configuration Service updates the Kubernetes `ConfigMap`.
158-
- ConfigMap update and interaction with kubelet cache: In Azure Spring Apps, this `ConfigMap` is mounted as a data volume to the relevant application. However, there's a natural delay in this process due to the frequency at which the kubelet refreshes its cache to recognize changes in `ConfigMap`.
158+
- `ConfigMap` update and interaction with kubelet cache: In Azure Spring Apps, this `ConfigMap` is mounted as a data volume to the relevant application. However, there's a natural delay in this process due to the frequency at which the kubelet refreshes its cache to recognize changes in `ConfigMap`.
159159
- Application reads updated configuration: Your application running in the Azure Spring Apps environment can access the updated configuration values. The existing beans in the Spring Context aren't automatically refreshed to use the updated configurations.
160160

161161
These stages are summarized in the following diagram:
@@ -377,14 +377,16 @@ az spring application-configuration-service delete \
377377

378378
## Examine configuration file in ConfigMap
379379

380-
The following section shows you how to examine the content of the configuration file pulled by Application Configuration Service from upstream Git repositories in related Kubernetes `ConfigMap`. For more information, see the [Refresh strategies](#refresh-strategies) section of this article.
380+
The following section shows you how to examine the content of the configuration file pulled by Application Configuration Service from upstream Git repositories in the related Kubernetes `ConfigMap`. For more information, see the [Refresh strategies](#refresh-strategies) section of this article.
381381

382382
### Assign an Azure role
383383

384-
Use the following steps to assign the `Azure Spring Apps Application Configuration Service Config File Pattern Reader Role`.
384+
First, you must have the Azure role `Azure Spring Apps Application Configuration Service Config File Pattern Reader Role` assigned to you.
385385

386386
#### [Azure portal](#tab/azure-Portal)
387387

388+
Use the following steps to assign an Azure role:
389+
388390
1. Open the [Azure portal](https://portal.azure.com) and go to your Azure Spring Apps service instance.
389391

390392
1. In the navigation pane, select **Access Control (IAM)**.
@@ -403,6 +405,8 @@ Use the following steps to assign the `Azure Spring Apps Application Configurati
403405

404406
#### [Azure CLI](#tab/azure-CLI)
405407

408+
Use the following command to assign an Azure role:
409+
406410
```azurecli
407411
az role assignment create \
408412
--role "Azure Spring Apps Application Configuration Service Config File Pattern Reader Role" \
@@ -423,7 +427,7 @@ az spring application-configuration-service config show \
423427
--config-file-pattern <pattern>
424428
```
425429

426-
The command returns an output similar to the following example:
430+
This command produces JSON output similar to the following example:
427431

428432
```json
429433
{
@@ -436,15 +440,15 @@ The command returns an output similar to the following example:
436440
}
437441
```
438442

439-
You can also use this command with `--export-path {/path/to/target/folder}` parameter to export the configuration file to the specified folder. It supports both the relative path and the absolute path. If not specified, it takes the path of the current directory.
443+
You can also use this command with the `--export-path {/path/to/target/folder}` parameter to export the configuration file to the specified folder. It supports both relative paths and absolute paths. If you don't specify the path, the command uses the path of the current directory by default.
440444

441445
## Examine configuration file in the app
442446

443447
After you bind the app to the Application Configuration Service and set the [Pattern](#pattern) for the app deployment, as described in the [Use Application Configuration Service with applications](#use-application-configuration-service-with-applications) section of this article, the `ConfigMap` containing the configuration file for the pattern should be mounted to the application container. Use the following steps to check the configuration files in each instance of the app deployment:
444448

445449
1. Connect to one of the application instances. For more information, see [Connect to an app instance for troubleshooting](./how-to-connect-to-app-instance-for-troubleshooting.md).
446450

447-
1. Use the `echo $AZURE_SPRING_APPS_CONFIG_FILE_PATH` command to find the folders containing the configuration files. A list of locations shows up separated by comma, as shown in the following example:
451+
1. Use the `echo $AZURE_SPRING_APPS_CONFIG_FILE_PATH` command to find the folders containing the configuration files. A list of locations shows up separated by commas, as shown in the following example:
448452

449453
```output
450454
$ echo $AZURE_SPRING_APPS_CONFIG_FILE_PATH

‎articles/spring-apps/enterprise/media/how-to-enterprise-application-configuration-service/application-configuration-service-config-pattern-file-reader-role.png

18.1 KB
Loading

0 commit comments

Comments
 (0)