Skip to content

Commit 1f3a90e

Browse files
authored
Merge pull request #251257 from RichardChen820/appconfig/junbchen/revertFileStyle
Revert file style configMap
2 parents e2ef2e1 + ceaf9b4 commit 1f3a90e

File tree

1 file changed

+0
-128
lines changed

1 file changed

+0
-128
lines changed

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

Lines changed: 0 additions & 128 deletions
Original file line numberDiff line numberDiff line change
@@ -31,14 +31,6 @@ The `spec.target` property has the following child property.
3131
|Name|Description|Required|Type|
3232
|---|---|---|---|
3333
|configMapName|The name of the ConfigMap to be created|true|string|
34-
|configMapData|The setting that specifies how the retrieved data should be populated in the generated ConfigMap|false|object|
35-
36-
If the `spec.target.configMapData` property is not set, the generated ConfigMap will be populated with the list of key-values retrieved from Azure App Configuration, which allows the ConfigMap to be consumed as environment variables. Update this property if you wish to consume the ConfigMap as a mounted file. This property has the following child properties.
37-
38-
|Name|Description|Required|Type|
39-
|---|---|---|---|
40-
|type|The setting that indicates how the retrieved data is constructed in the generated ConfigMap. The allowed values include `default`, `json`, `yaml` and `properties`|optional|string|
41-
|key|The key name of the retrieved data when the `type` is set to `json`, `yaml` or `properties`. Set it to the file name if the ConfigMap is set up to be consumed as a mounted file|conditional|string|
4234

4335
If the `spec.auth` property isn't set, the system-assigned managed identity is used. It has the following child properties. Only one authentication method should be set.
4436

@@ -290,124 +282,4 @@ spec:
290282
label: common
291283
- key: sentinelKey
292284
label: development
293-
```
294-
295-
### Consume ConfigMap
296-
297-
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 default, 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.
298-
299-
The following examples show how the data is populated in the generated ConfigMap with different settings of the `configMapData.type` property.
300-
301-
Assuming an App Configuration store has these key-values:
302-
303-
|key|value|
304-
|---|---|
305-
|key1|value1|
306-
|key2|value2|
307-
|key3|value3|
308-
309-
#### [default](#tab/default)
310-
311-
and the `configMapData.type` property is absent or set to `default`,
312-
313-
``` yaml
314-
apiVersion: azconfig.io/v1beta1
315-
kind: AzureAppConfigurationProvider
316-
metadata:
317-
name: appconfigurationprovider-sample
318-
spec:
319-
endpoint: <your-app-configuration-store-endpoint>
320-
target:
321-
configMapName: configmap-created-by-appconfig-provider
322-
```
323-
324-
the generated ConfigMap will be populated with the following data:
325-
326-
``` yaml
327-
data:
328-
key1: value1
329-
key2: value2
330-
key3: value3
331-
```
332-
333-
#### [json](#tab/json)
334-
335-
and the `configMapData.type` property is set to `json`,
336-
337-
``` yaml
338-
apiVersion: azconfig.io/v1beta1
339-
kind: AzureAppConfigurationProvider
340-
metadata:
341-
name: appconfigurationprovider-sample
342-
spec:
343-
endpoint: <your-app-configuration-store-endpoint>
344-
target:
345-
configMapName: configmap-created-by-appconfig-provider
346-
configMapData:
347-
type: json
348-
key: appSettings.json
349-
```
350-
351-
the generated ConfigMap will be populated with the following data:
352-
353-
``` yaml
354-
data:
355-
appSettings.json: >-
356-
{"key1":"value1","key2":"value2","key3":"value3"}
357-
```
358-
359-
#### [yaml](#tab/yaml)
360-
361-
and the `configMapData.type` property is set to `yaml`,
362-
363-
``` yaml
364-
apiVersion: azconfig.io/v1beta1
365-
kind: AzureAppConfigurationProvider
366-
metadata:
367-
name: appconfigurationprovider-sample
368-
spec:
369-
endpoint: <your-app-configuration-store-endpoint>
370-
target:
371-
configMapName: configmap-created-by-appconfig-provider
372-
configMapData:
373-
type: yaml
374-
key: appSettings.yaml
375-
```
376-
377-
the generated ConfigMap will be populated with the following data:
378-
379-
``` yaml
380-
data:
381-
appSettings.yaml: >-
382-
key1: value1
383-
key2: value2
384-
key3: value3
385-
```
386-
387-
#### [properties](#tab/properties)
388-
389-
and the `configMapData.type` property is set to `properties`,
390-
391-
``` yaml
392-
apiVersion: azconfig.io/v1beta1
393-
kind: AzureAppConfigurationProvider
394-
metadata:
395-
name: appconfigurationprovider-sample
396-
spec:
397-
endpoint: <your-app-configuration-store-endpoint>
398-
target:
399-
configMapName: configmap-created-by-appconfig-provider
400-
configMapData:
401-
type: properties
402-
key: app.properties
403-
```
404-
405-
the generated ConfigMap will be populated with the following data:
406-
407-
``` yaml
408-
data:
409-
app.properties: >-
410-
key1=value1
411-
key2=value2
412-
key3=value3
413285
```

0 commit comments

Comments
 (0)