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/deployment-environments/how-to-configure-catalog.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
---
2
-
title: Add a catalog from a GitHub or Azure DevOps repository
2
+
title: Add a catalog from a GitHub or Azure Repos repository
3
3
titleSuffix: Azure Deployment Environments
4
4
description: Learn how to add a catalog in your Azure Deployment Environments dev center or project to provide environment definitions for your developers.
5
5
ms.service: azure-deployment-environments
6
6
ms.custom: build-2023, build-2024
7
7
author: RoseHJM
8
8
ms.author: rosemalcolm
9
-
ms.date: 05/10/2024
9
+
ms.date: 11/25/2024
10
10
ms.topic: how-to
11
11
#customer intent: As a platform engineer, I want to learn how to add a catalog in my Azure Deployment Environments dev center or project so that I can provide environment definitions for my developers.
12
12
---
@@ -15,7 +15,7 @@ ms.topic: how-to
15
15
16
16
This article explains how to add and configure a [catalog](./concept-environments-key-concepts.md#catalogs) for your Azure Deployment Environments dev center or project.
17
17
18
-
Catalogs help you provide a set of curated infrastructure-as-code(IaC) templates, known as environment definitions for your development teams to create environments. You can attach your own source control repository from GitHub or Azure DevOps as a catalog and specify the folder with your environment definitions. Deployment Environments scans the folder for environment definitions and makes them available for dev teams to create environments.
18
+
Catalogs help you provide a set of curated infrastructure-as-code(IaC) templates, known as environment definitions for your development teams to create environments. You can attach your own source control repository from GitHub or Azure Repos as a catalog and specify the folder with your environment definitions. Deployment Environments scans the folder for environment definitions and makes them available for dev teams to create environments.
19
19
20
20
To further secure your templates, the catalog is encrypted; Azure Deployment Environments supports encryption at rest with platform-managed encryption keys, which Microsoft for Azure Services manages.
21
21
@@ -516,6 +516,8 @@ When you configure a catalog to sync automatically, Deployment Environments scan
516
516
517
517
:::image type="content" source="media/how-to-configure-catalog/catalog-automatic-sync-pane.png" alt-text="Screenshot showing the edit details pane for a catalog, with Automatically sync this catalog highlighted." lightbox="media/how-to-configure-catalog/catalog-automatic-sync-pane.png":::
518
518
519
+
If an autosync fails, you should perform a manual sync. Deployment Environments doesn't make any further autosync attempts until a manual sync succeeds.
520
+
519
521
## Delete a catalog
520
522
521
523
You can delete a catalog to remove it from the Azure Deployment Environments dev center or project. Templates in a deleted catalog aren't available to development teams when they deploy new environments. Update the environment definition reference for any existing environments that were created by using the environment definitions in the deleted catalog. If the reference isn't updated and the environment is redeployed, the deployment fails.
@@ -554,13 +556,13 @@ In the Azure portal, you can get more information about the catalog sync status
554
556
555
557
1. In the **Status** column, select the status link for the catalog that synced but reports a warning.
556
558
557
-
:::image type="content" source="media/how-to-configure-catalog/catalog-items-errors.png" alt-text="Screenshot showing the Catalogs pane, with Errors in 3 items highlighted." lightbox="media/how-to-configure-catalog/catalog-items-errors.png":::
559
+
:::image type="content" source="media/how-to-configure-catalog/catalog-items-errors.png" alt-text="Screenshot showing the Catalogs pane, with Errors in three items highlighted." lightbox="media/how-to-configure-catalog/catalog-items-errors.png":::
558
560
559
561
1. You see a details pane that shows the changes in the last sync, the number of item errors, and the type and source of each error.
1. You can view items that have synced successfully from a catalog that also reports sync errors. From the **Catalogs** pane, select the catalog name.
565
+
1. You can view items that synced successfully from a catalog that also reports sync errors. From the **Catalogs** pane, select the catalog name.
564
566
565
567
:::image type="content" source="media/how-to-configure-catalog/catalog-with-error-view-successful-items.png" alt-text="Screenshot showing the Catalog pane, with a catalog name highlighted." lightbox="media/how-to-configure-catalog/catalog-with-error-view-successful-items.png":::
0 commit comments