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
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/reference-kubernetes-provider.md
+10-24Lines changed: 10 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -297,9 +297,9 @@ spec:
297
297
298
298
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.
299
299
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.
301
301
302
-
Assume these key-values are selected from Azure App Configuration:
302
+
Assuming an App Configuration store has these key-values:
303
303
304
304
|key|value|
305
305
|---|---|
@@ -309,7 +309,7 @@ Assume these key-values are selected from Azure App Configuration:
309
309
310
310
#### [default](#tab/default)
311
311
312
-
`configMapData.type`property absent or set to `default`.
312
+
and the `configMapData.type` property is absent or set to `default`,
0 commit comments