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/howto-import-export-data.md
+36-24Lines changed: 36 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: azure-app-configuration
5
5
author: maud-lv
6
6
ms.service: azure-app-configuration
7
7
ms.topic: conceptual
8
-
ms.date: 02/25/2022
8
+
ms.date: 04/06/2022
9
9
ms.author: malev
10
10
---
11
11
@@ -21,43 +21,49 @@ You can import or export data using either the [Azure portal](https://portal.azu
21
21
22
22
Import brings configuration data into an App Configuration store from an existing source. Use the import function to migrate data into an App Configuration store or aggregate data from multiple sources. App Configuration supports importing from another App Configuration store, an App Service resource or a configuration file in JSON, YAML or .properties.
23
23
24
-
# [Portal](#tab/azure-portal)
24
+
###[Portal](#tab/azure-portal)
25
25
26
26
From the Azure portal, follow these steps:
27
27
28
28
1. Browse to your App Configuration store, and select **Import/export** from the **Operations** menu.
29
29
30
-
1. On the **Import** tab, select **Configuration file** under **Source service**. Other options are **App Configuration** and **File services**.
30
+
:::image type="content" source="./media/import-file.png" alt-text="Screenshot of the Azure portal, importing a file.":::
31
31
32
-
1.Select **For language**: .NET or Java (Spring) or other, and select your desired input type—JSON, YAML or .properties.
32
+
1.On the **Import**tab, select **Configuration file** under **Source service**. Other options are **App Configuration** and **App Services**.
33
33
34
-
1.Select the **Folder** icon, and browse to the file to import.
34
+
1.Fill out the form with the following parameters:
35
35
36
-
:::image type="content" source="./media/import-file.png" alt-text="Screenshot of the Azure portal, importing a file.":::
| For language | Choose the language of the file you're importing between .NET, Java (Spring) and Other. | .NET |
39
+
| File type | Select the type of file you're importing between YAML, properties or JSON. | JSON |
37
40
38
-
1. Select a**Separator**, and optionally enter a **Prefix** to use for imported key names.
41
+
1. Select the**Folder** icon, and browse to the file to import.
39
42
40
-
* A separator is a character used to separate values in a file to distribute them in a table. Select a period (.), a comma (,), a colon (:), a semicolon (;), a forward slash (/) or a dash (-).
41
-
* A key prefix is the beginning part of a key.
43
+
1. Fill out the next part of the form:
42
44
43
-
1. Optionally, select a **Label** to assign to your imported key-value pairs.
| Separator | The separator is the character parsed in your imported configuration file to separate key-values which will be added to your configuration store. Select one of the following options: `.`, `,`,`:`, `;`, `/`, `-`. | : |
48
+
| Prefix | Optional. A key prefix is the beginning part of a key. Prefixes can be used to manage groups of keys in a configuration store. | TestApp:Settings:Backgroundcolor|
49
+
| Label | Optional. Select an existing label or enter a new label that will be assigned to your imported key-values. | prod |
50
+
| Content type | Optional. Indicate if the file you're importing is a Key Vault reference or a JSON file. For more information about Key Vault references, go to [Use Key Vault references in an ASP.NET Core app](/azure/azure-app-configuration/use-key-vault-references-dotnet-core). | JSON (application/json) |
45
51
46
-
:::image type="content" source="./media/import-file-complete.png" alt-text="Screenshot of the Azure portal, file import completed":::
52
+
1. Select **Apply** to proceed with the import.
47
53
48
-
# [Azure CLI](#tab/azure-cli)
54
+
###[Azure CLI](#tab/azure-cli)
49
55
50
56
Use the Azure CLI as explained below to import App Configuration data. If you don't have the Azure CLI installed locally, you can optionally use [Azure Cloud Shell](/azure/cloud-shell/overview). Specify the source of the data: `appconfig`, `appservice` or `file`. Optionally specify a source label with `--src-label` and a label to apply with `--label`.
51
57
52
58
Import all keys and feature flags from a file and apply test label.
53
59
54
-
```python
60
+
```azurecli
55
61
az appconfig kv import --name <your-app-config-store-name> --label test --source file --path D:/abc.json --format json
56
62
```
57
63
58
64
Import all keys with label test and apply test2 label.
59
65
60
-
```python
66
+
```azurecli
61
67
az appconfig kv import --name <your-app-config-store-name> --source appconfig --src-label test --label test2 --src-name <another-app-config-store-name>
62
68
```
63
69
@@ -75,29 +81,35 @@ For more details and examples, go to [az appconfig kv import](/cli/azure/appconf
75
81
76
82
## Export data
77
83
78
-
Export writes configuration data stored in App Configuration to another destination. Use the export function, for example, to save data in an App Configuration store to a file that's embedded with your application code during deployment. You can export data from an App Configuration store, an App Service resource or a configuration in JSON, YAML or .properties.
84
+
Export writes configuration data stored in App Configuration to another destination. Use the export function, for example, to save data from an App Configuration store to a file that can be embedded in your application code during deployment. You can export data from an App Configuration store, an App Service resource or a configuration file in JSON, YAML or .properties.
79
85
80
-
# [Portal](#tab/azure-portal)
86
+
###[Portal](#tab/azure-portal)
81
87
82
88
From the [Azure portal](https://portal.azure.com), follow these steps:
83
89
84
90
1. Browse to your App Configuration store, and select **Import/export**.
85
91
86
92
1. On the **Export** tab, select **Target service** > **Configuration file**.
87
93
88
-
1. Optionally enter a **Prefix** select a **label** and a point-in-time for keys to be exported.
89
-
* Prefix: it's the beginning part of a key. Leave blank or fill out to restrict data to export.
90
-
* Label: Labels can be assigned to keys to define different values for the same key. Leave blank to select all keys without a label, or select a label in the dropdown box. [Learn more about labels](howto-labels-aspnet-core.md).
91
-
* Specific time: leave blank or fill out to export key data as from a specific point in time.
94
+
1. Fill out the form with the following parameters:
| Prefix | Optional. A key prefix is the beginning part of a key. Enter a prefix to restrict your export to key-values with the specified prefix. | TestApp:Settings:Backgroundcolor|
99
+
| From label | Optional. Select an existing label to restrict your export to key-values with a specific label. If you don't select a label, only key-values without a label will be exported. See note below. | prod |
100
+
| At a specific time | Optional. Fill out to export key-values from a specific point in time. | 01/28/2021 12:00:00 AM |
101
+
| File type | Select the type of file you' a're importing between YAML, properties or JSON. | JSON |
102
+
| Separator | The separator is the character parsed in your imported configuration file to separate key-values which will be added to your configuration store. Select one of the following options: `.`, `,`,`:`, `;`, `/`, `-`. | ; |
103
+
|
104
+
92
105
> [!IMPORTANT]
93
-
> If the keys you want to export have labels, do select the corresponding labels. If you don't select a label, only keys without labels will be exported. You may need create several exports to get all the desired data, according to the labels you need.
94
-
1. Select a **File type** > **Separator**.
106
+
> If you don't select a 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, so to export keys with multiple labels, you may need to export multiple times, once per label you select.
95
107
96
108
1. Select **Export** to finish the export.
97
109
98
110
:::image type="content" source="./media/export-file-complete.png" alt-text="Screenshot of the Azure portal, exporting a file":::
99
111
100
-
# [Azure CLI](#tab/azure-cli)
112
+
###[Azure CLI](#tab/azure-cli)
101
113
102
114
Use the Azure CLI as explained below to export configurations from App Configuration to another place. If you don't have the Azure CLI installed locally, you can optionally use [Azure Cloud Shell](/azure/cloud-shell/overview). Specify the destination of the data: `appconfig`, `appservice` or `file`. Specify a label for the data you want to export with `--label` or export data with no label by not entering a label.
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/quickstart-dotnet-core-app.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
title: Quickstart for Azure App Configuration with .NET Core | Microsoft Docs
3
3
description: In this quickstart, create a .NET Core app with Azure App Configuration to centralize storage and management of application settings separate from your code.
4
4
services: azure-app-configuration
5
-
author: AlexandraKemperMS
5
+
author: maud-lv
6
6
ms.service: azure-app-configuration
7
7
ms.devlang: csharp
8
8
ms.topic: quickstart
9
9
ms.custom: devx-track-csharp, mode-other
10
-
ms.date: 09/28/2020
11
-
ms.author: alkemper
10
+
ms.date: 04/05/2022
11
+
ms.author: malev
12
12
#Customer intent: As a .NET Core developer, I want to manage all my app settings in one place.
13
13
---
14
14
# Quickstart: Create a .NET Core app with App Configuration
@@ -24,15 +24,15 @@ In this quickstart, you incorporate Azure App Configuration into a .NET Core con
0 commit comments