Skip to content

Commit da31712

Browse files
maud-lvmaud-lv
committed
Fix indentation
1 parent 645c3f6 commit da31712

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

‎articles/azure-app-configuration/howto-import-export-data.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -290,13 +290,13 @@ From the [Azure portal](https://portal.azure.com), follow these steps:
290290
291291
1. Fill out the form with the following parameters:
292292
293-
| Parameter | Description | Example |
294-
|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|
295-
| Prefix | Optional. This prefix will be trimmed from the keys. A key prefix is the beginning part of a key. Prefixes can be used to manage groups of keys in a configuration store. | *TestApp:* |
296-
| From label | Select an existing label to restrict your export to key-values with a specific label. If you don't select a label, by default only key-values with the "No Label" label will be exported. See note below. | *prod* |
297-
| At a specific time | Optional. Fill out to import key-values from a specific point in time. This is the point in time of the resource you selected in the previous step. Format: "YYYY-MM-DDThh:mm:ssZ". | *07/28/2022 12:00:00 AM* |
298-
| File type | Select the type of file you're exporting between Yaml, Properties or Json. | *JSON* |
299-
| Separator | The separator is the delimiter for flattening the key-values to Json/Yaml. It supports the configuration's hierarchical structure and doesn't apply to property files and feature flags. Select one of the following options: *.*, *,*, *:*, *;*, */*, *-*, *_*, *—*, or *(No separator)*. | *;* |
293+
| Parameter | Description | Example |
294+
|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|
295+
| Prefix | Optional. This prefix will be trimmed from the keys. A key prefix is the beginning part of a key. Prefixes can be used to manage groups of keys in a configuration store. | *TestApp:* |
296+
| From label | Select an existing label to restrict your export to key-values with a specific label. If you don't select a label, by default only key-values with the "No Label" label will be exported. See note below. | *prod* |
297+
| At a specific time | Optional. Fill out to import key-values from a specific point in time. This is the point in time of the resource you selected in the previous step. Format: "YYYY-MM-DDThh:mm:ssZ". | *07/28/2022 12:00:00 AM* |
298+
| File type | Select the type of file you're exporting between Yaml, Properties or Json. | *JSON* |
299+
| Separator | The separator is the delimiter for flattening the key-values to Json/Yaml. It supports the configuration's hierarchical structure and doesn't apply to property files and feature flags. Select one of the following options: *.*, *,*, *:*, *;*, */*, *-*, *_*, *—*, or *(No separator)*. | *;* |
300300
301301
> [!IMPORTANT]
302302
> If you don't select a *From label*, only keys without labels will be exported. To export a key-value with a label, you must select its label. Note that you can only select one label per export in portal, in case you want to export the key-values with all labels specified please use CLI.
@@ -324,10 +324,10 @@ From the Azure CLI, follow the steps below. If you don't have the Azure CLI inst
324324
325325
1. Optionally also add the following parameters:
326326
327-
| Parameter | Description | Example |
328-
|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
329-
| `--separator` | Optional. The separator is the delimiter for flattening the key-values to Json/Yaml. It's required for exporting hierarchical structure and will be ignored for property files and feature flags. Select one of the following options: `.`, `,`, `:`, `;`, `/`, `-`, `_`, `—`. | `;` |
330-
| `--prefix` | Optional. Prefix to be trimmed from keys. A key prefix is the beginning part of a key. Prefixes can be used to manage groups of keys in a configuration store. Prefix will be ignored for feature flags. | `TestApp:` |
327+
| Parameter | Description | Example |
328+
|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
329+
| `--separator` | Optional. The separator is the delimiter for flattening the key-values to Json/Yaml. It's required for exporting hierarchical structure and will be ignored for property files and feature flags. Select one of the following options: `.`, `,`, `:`, `;`, `/`, `-`, `_`, `—`. | `;` |
330+
| `--prefix` | Optional. Prefix to be trimmed from keys. A key prefix is the beginning part of a key. Prefixes can be used to manage groups of keys in a configuration store. Prefix will be ignored for feature flags. | `TestApp:` |
331331
332332
Example: export all keys and feature flags with label "prod" to a JSON file.
333333

0 commit comments

Comments
 (0)