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
title: Azure Deployment Environments and Microsoft Dev Box common elements
3
-
description: Discover the components shared by Azure Deployment Environments and Microsoft Dev Box.
3
+
description: Discover the components that are shared by Azure Deployment Environments Preview and Microsoft Dev Box.
4
4
ms.service: deployment-environments
5
5
ms.custom: ignite-2022
6
6
ms.topic: conceptual
7
7
ms.author: rosemalcolm
8
8
author: RoseHJM
9
9
ms.date: 01/26/2022
10
10
---
11
-
# Components common to Azure Deployment Environments and Microsoft Dev Box
11
+
# Components common to Azure Deployment Environments and Microsoft Dev Box
12
12
13
13
> [!TIP]
14
-
> Welcome to the **Azure Deployment Environments** documentation. If you're looking for information about **Microsoft Dev Box**, follow this link: [*Components common to Microsoft Dev Box and Azure Deployment Environments*](../dev-box/concept-common-components.md).
14
+
> Welcome to the *Azure Deployment Environments Preview* documentation.
15
+
>
16
+
> If you're looking for information about *Microsoft Dev Box*, go to [Components common to Microsoft Dev Box and Azure Deployment Environments](../dev-box/concept-common-components.md).
Copy file name to clipboardExpand all lines: articles/deployment-environments/how-to-configure-catalog.md
+25-26Lines changed: 25 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.topic: how-to
12
12
13
13
# Add and configure a catalog
14
14
15
-
Learn how to add and configure a [catalog](./concept-environments-key-concepts.md#catalogs) in your Azure Deployment Environments Preview dev center. You can use a catalog to provide your development teams with a curated set of infrastructure as code (IaC) templates called [*catalog items*](./concept-environments-key-concepts.md#catalog-items).
15
+
Learn how to add and configure a [catalog](./concept-environments-key-concepts.md#catalogs) in your Azure Deployment Environments Preview dev center. You can use a catalog to provide your development teams with a curated set of infrastructure as code (IaC) templates called [catalog items](./concept-environments-key-concepts.md#catalog-items).
16
16
17
17
For more information about catalog items, see [Add and configure a catalog item](./configure-catalog-item.md).
18
18
@@ -27,9 +27,9 @@ In this article, you learn how to:
27
27
28
28
> [!div class="checklist"]
29
29
>
30
-
> - Add a catalog
31
-
> - Update a catalog
32
-
> - Delete a catalog
30
+
> - Add a catalog.
31
+
> - Update a catalog.
32
+
> - Delete a catalog.
33
33
34
34
> [!IMPORTANT]
35
35
> Azure Deployment Environments currently is in preview. For legal terms that apply to Azure features that are in beta, in preview, or otherwise are not yet released into general availability, see the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
@@ -39,7 +39,7 @@ In this article, you learn how to:
39
39
To add a catalog, you complete these tasks:
40
40
41
41
- Get the clone URL for your repository.
42
-
- Create a personal access token
42
+
- Create a personal access token.
43
43
- Store the personal access token as a key vault secret in Azure Key Vault.
44
44
- Add your repository as a catalog.
45
45
@@ -53,13 +53,13 @@ You can choose from two types of repositories:
53
53
#### Get the clone URL of a GitHub repository
54
54
55
55
1. Go to the home page of the GitHub repository that contains the template definitions.
56
-
1.[Get the clone URL](/azure/devops/repos/git/clone#get-the-clone-url-of-a-github-repo).
56
+
1.[Get the GitHub repo clone URL](/azure/devops/repos/git/clone#get-the-clone-url-of-a-github-repo).
57
57
1. Copy and save the URL. You use it later.
58
58
59
59
#### Get the clone URL of an Azure DevOps repository
60
60
61
61
1. Go to the home page of your team collection (for example, `https://contoso-web-team.visualstudio.com`), and then select your project.
62
-
1.[Get the clone URL](/azure/devops/repos/git/clone#get-the-clone-url-of-an-azure-repos-git-repo).
62
+
1.[Get the Git repo clone URL](/azure/devops/repos/git/clone#get-the-clone-url-of-an-azure-repos-git-repo).
63
63
1. Copy and save the URL. You use it later.
64
64
65
65
### Create a personal access token
@@ -70,24 +70,23 @@ Next, create a personal access token. Depending on the type of repository you us
70
70
71
71
1. Go to the home page of the GitHub repository that contains the template definitions.
72
72
1. In the upper-right corner of GitHub, select the profile image, and then select **Settings**.
73
-
1. In the left sidebar, select **Developer settings**.
74
-
1. In the left sidebar, select **Personal access tokens**.
73
+
1. On the left sidebar, select **Developer settings** > **Personal access tokens**.
75
74
1. Select **Generate new token**.
76
-
1.In**New personal access token**, in **Note**, enter a description for your token.
75
+
1.On**New personal access token**, in **Note**, enter a description for your token.
77
76
1. In the **Expiration** dropdown, select an expiration for your token.
78
77
1. For a private repository, under **Select scopes**, select the **repo** scope.
79
78
1. Select **Generate token**.
80
79
1. Save the generated token. You use the token later.
81
80
82
81
#### Create a personal access token in Azure DevOps
83
82
84
-
1. Go to the home page of your team collection (for example, `https://contoso-web-team.visualstudio.com`), and then select your project.
83
+
1. Go to the home page of your team collection (for example, `https://contoso-web-team.visualstudio.com`) and select your project.
85
84
1. Create a [personal access token](/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate#create-a-pat).
86
85
1. Save the generated token. You use the token later.
87
86
88
87
### Store the personal access token as a key vault secret
89
88
90
-
To store the personal access token, you generated as a [key vault secret](../key-vault/secrets/about-secrets.md) and copy the secret identifier:
89
+
To store the personal access token that you generated as a [key vault secret](../key-vault/secrets/about-secrets.md) and copy the secret identifier:
91
90
92
91
1. Create a [key vault](../key-vault/general/quick-create-portal.md#create-a-vault).
93
92
1. Add the personal access token as a [secret to the key vault](../key-vault/secrets/quick-create-portal.md#add-a-secret-to-key-vault).
@@ -97,46 +96,46 @@ To store the personal access token, you generated as a [key vault secret](../key
97
96
98
97
1. In the [Azure portal](https://portal.azure.com/), go to your dev center.
99
98
1. Ensure that the [identity](./how-to-configure-managed-identity.md) that's attached to the dev center has [access to the key vault secret](./how-to-configure-managed-identity.md#grant-the-managed-identity-access-to-the-key-vault-secret) where your personal access token is stored.
100
-
1.In the left menu under **Environment configuration**, select **Catalogs**, and then select **Add**.
101
-
1.In**Add catalog**, enter the following information, and then select **Add**:
99
+
1.On the left menu under **Environment configuration**, select **Catalogs**, and then select **Add**.
100
+
1.On**Add catalog**, enter the following information, and then select **Add**:
102
101
103
102
| Field | Value |
104
103
| ----- | ----- |
105
104
|**Name**| Enter a name for the catalog. |
106
-
|**Git clone URI**| Enter or paste the [clone URL](#get-the-clone-url-for-your-repository) for either your GitHub repository or your Azure DevOps repository.<br/>*Sample Catalog Example:*https://github.com/Azure/deployment-environments.git|
107
-
|**Branch**| Enter the repository branch to connect to.<br/>*Sample Catalog Example:* main|
108
-
|**Folder path**| Enter the folder path relative to the clone URI that contains subfolders with your catalog items. </br> This folder path should be the path to the folder that contains the subfolders with the catalog item manifests, and not the path to the folder with the catalog item manifest itself.<br/>*Sample Catalog Example:* /Environments</br> The folder path can begin with or without a '/'.|
109
-
|**Secret identifier**| Enter the [secret identifier](#create-a-personal-access-token) that contains your personal access token for the repository.</br>When you copy a Secret Identifier, the connection string includes a version identifier at the end, like this: https://contoso-kv.vault.azure.net/secrets/GitHub-repo-pat/9376b432b72441a1b9e795695708ea5a. </br>Removing the version identifier ensures that Deployment Environments fetches the latest version of the secret from the key vault. If your PAT expires, only the key vault needs to be updated. </br> *Example secret identifier:https://contoso-kv.vault.azure.net/secrets/GitHub-repo-pat*|
105
+
|**Git clone URI**| Enter or paste the [clone URL](#get-the-clone-url-for-your-repository) for either your GitHub repository or your Azure DevOps repository.<br/>*Sample catalog example:*`https://github.com/Azure/deployment-environments.git`|
106
+
|**Branch**| Enter the repository branch to connect to.<br/>*Sample catalog example:*`main`|
107
+
|**Folder path**| Enter the folder path relative to the clone URI that contains subfolders that hold your catalog items. <br /> This folder path should be the path to the folder that contains the subfolders that have the catalog item manifests, and not the path to the folder that has the catalog item manifest itself.<br/>*Sample catalog example:*`/Environments`<br /> The folder path can begin with or without a forward slash (`/`).|
108
+
|**Secret identifier**| Enter the [secret identifier](#create-a-personal-access-token) that contains your personal access token for the repository.<br /> When you copy a secret identifier, the connection string includes a version identifier at the end, like in this example: `https://contoso-kv.vault.azure.net/secrets/GitHub-repo-pat/9376b432b72441a1b9e795695708ea5a`.<br />Removing the version identifier ensures that Deployment Environments fetches the latest version of the secret from the key vault. If your personal access token expires, only the key vault needs to be updated. <br />*Example secret identifier:*`https://contoso-kv.vault.azure.net/secrets/GitHub-repo-pat`|
110
109
111
110
:::image type="content" source="media/how-to-configure-catalog/add-catalog-form-inline.png" alt-text="Screenshot that shows how to add a catalog to a dev center." lightbox="media/how-to-configure-catalog/add-catalog-form-expanded.png":::
112
111
113
-
1.In**Catalogs** for the dev center, verify that your catalog appears. If the connection is successful, **Status** is **Connected**.
112
+
1.On**Catalogs** for the dev center, verify that your catalog appears. If the connection is successful, **Status** is **Connected**.
114
113
115
114
## Update a catalog
116
115
117
-
If you update the ARM template contents or definition in the attached repository, you can provide the latest set of catalog items to your development teams by syncing the catalog.
116
+
If you update the Azure Resource Manager template (ARM template) contents or definition in the attached repository, you can provide the latest set of catalog items to your development teams by syncing the catalog.
118
117
119
118
To sync an updated catalog:
120
119
121
-
1.In the left menu for your dev center, under **Environment configuration**, select **Catalogs**,
120
+
1.On the left menu for your dev center, under **Environment configuration**, select **Catalogs**,
122
121
1. Select the specific catalog, and then select **Sync**. The service scans through the repository and makes the latest list of catalog items available to all the associated projects in the dev center.
123
122
124
123
## Delete a catalog
125
124
126
-
You can delete a catalog to remove it from the dev center. Templates in a deleted catalog are not available to development teams when they deploy new environments. Update the catalog item reference for any existing environments that were created by using the catalog items in the deleted catalog. If the reference isn't updated and the environment is redeployed, the deployment fails.
125
+
You can delete a catalog to remove it from the dev center. Templates in a deleted catalog aren't available to development teams when they deploy new environments. Update the catalog item reference for any existing environments that were created by using the catalog items in the deleted catalog. If the reference isn't updated and the environment is redeployed, the deployment fails.
127
126
128
127
To delete a catalog:
129
128
130
-
1.In the left menu for your dev center, under **Environment configuration**, select **Catalogs**.
129
+
1.On the left menu for your dev center, under **Environment configuration**, select **Catalogs**.
131
130
1. Select the specific catalog, and then select **Delete**.
132
131
1. In the **Delete catalog** dialog, select **Continue** to delete the catalog.
133
132
134
133
## Catalog sync errors
135
134
136
135
When you add or sync a catalog, you might encounter a sync error. A sync error indicates that some or all the catalog items have errors. Use the Azure CLI or the REST API to GET the catalog. The GET response shows you the type of errors:
137
136
138
-
- Ignored catalog items that were detected to be duplicates
139
-
- Invalid catalog items that failed due to schema, reference, or validation errors
137
+
- Ignored catalog items that were detected to be duplicates.
138
+
- Invalid catalog items that failed due to schema, reference, or validation errors.
140
139
141
140
### Resolve ignored catalog item errors
142
141
@@ -152,7 +151,7 @@ An invalid catalog item error might occur for various reasons:
152
151
153
152
- Ensure that the manifest's engine type is correctly configured as `ARM`.
154
153
- Ensure that the catalog item name is between 3 and 63 characters.
155
-
- Ensure that the catalog item name includes only characters that are valid for a URL: alphanumeric characters and the symbols `~``!``,``.``'``;``:``=``-``_``+``)``(``*``&``$``@`.
154
+
- Ensure that the catalog item name includes only characters that are valid for a URL, which are alphanumeric characters and these symbols:`~``!``,``.``'``;``:``=``-``_``+``(``)``*``&``$``@`
156
155
157
156
-**Reference errors**. Ensure that the template path that the manifest references is a valid relative path to a file in the repository.
0 commit comments