Skip to content

Commit d6590f7

Browse files
Resolve comments
1 parent b5f0349 commit d6590f7

File tree

1 file changed

+10
-24
lines changed

1 file changed

+10
-24
lines changed

articles/azure-app-configuration/reference-kubernetes-provider.md

Lines changed: 10 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -297,9 +297,9 @@ spec:
297297

298298
Applications running in Kubernetes typically consume the ConfigMap either as environment variables or as configuration files. If the `configMapData.type` property is absent or is set to environment variables, the ConfigMap is populated with the itemized list of data retrieved from Azure App Configuration, which can be easily consumed as environment variables. If the `configMapData.type` property is set to json, yaml or properties, data retrieved from Azure App Configuration is grouped into one item with key name specified by the `configMapData.key` property in the generated ConfigMap, which can be consumed as a mounted file.
299299

300-
Following examples show you how the data is populated in the generated ConfigMap with different setting of `configMapData.type` property.
300+
The following examples show how the data is populated in the generated ConfigMap with different settings of the `configMapData.type` property.
301301

302-
Assume these key-values are selected from Azure App Configuration:
302+
Assuming an App Configuration store has these key-values:
303303

304304
|key|value|
305305
|---|---|
@@ -309,7 +309,7 @@ Assume these key-values are selected from Azure App Configuration:
309309

310310
#### [default](#tab/default)
311311

312-
`configMapData.type` property absent or set to `default`.
312+
and the `configMapData.type` property is absent or set to `default`,
313313

314314
``` yaml
315315
apiVersion: azconfig.io/v1beta1
@@ -321,22 +321,8 @@ spec:
321321
target:
322322
configMapName: configmap-created-by-appconfig-provider
323323
```
324-
or
325324

326-
``` yaml
327-
apiVersion: azconfig.io/v1beta1
328-
kind: AzureAppConfigurationProvider
329-
metadata:
330-
name: appconfigurationprovider-sample
331-
spec:
332-
endpoint: <your-app-configuration-store-endpoint>
333-
target:
334-
configMapName: configmap-created-by-appconfig-provider
335-
configMapData:
336-
type: default
337-
```
338-
339-
The generated ConfigMap is populated with the following data:
325+
the generated ConfigMap is populated with the following data:
340326

341327
``` yaml
342328
data:
@@ -347,7 +333,7 @@ data:
347333

348334
#### [json](#tab/json)
349335

350-
Set `configMapData.type` property to `json`.
336+
and the `configMapData.type` property is set to `json`,
351337

352338
``` yaml
353339
apiVersion: azconfig.io/v1beta1
@@ -363,7 +349,7 @@ spec:
363349
key: appSettings.json
364350
```
365351

366-
The generated ConfigMap is populated with the following data:
352+
the generated ConfigMap is populated with the following data:
367353

368354
``` yaml
369355
data:
@@ -373,7 +359,7 @@ data:
373359

374360
#### [yaml](#tab/yaml)
375361

376-
Set `configMapData.type` property to `yaml`.
362+
and the `configMapData.type` property is set to `yaml`,
377363

378364
``` yaml
379365
apiVersion: azconfig.io/v1beta1
@@ -389,7 +375,7 @@ spec:
389375
key: appSettings.yaml
390376
```
391377

392-
The generated ConfigMap is populated with the following data:
378+
the generated ConfigMap is populated with the following data:
393379

394380
``` yaml
395381
data:
@@ -401,7 +387,7 @@ data:
401387

402388
#### [properties](#tab/properties)
403389

404-
Set `configMapData.type` property to `properties`.
390+
and the `configMapData.type` property is set to `properties`,
405391

406392
``` yaml
407393
apiVersion: azconfig.io/v1beta1
@@ -417,7 +403,7 @@ spec:
417403
key: app.properties
418404
```
419405

420-
The generated ConfigMap is populated with the following data:
406+
the generated ConfigMap is populated with the following data:
421407

422408
``` yaml
423409
data:

0 commit comments

Comments
 (0)