Skip to content

Commit 1ed8f5f

Browse files
committed
Fix blocking issue
1 parent a154d9d commit 1ed8f5f

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

articles/dev-box/how-to-configure-catalog.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -26,15 +26,6 @@ To further secure your templates, the catalog is encrypted; Dev Box supports enc
2626
- To learn how to host a repository in GitHub, see [Get started with GitHub](https://docs.github.com/get-started).
2727
- To learn how to host a Git repository in an Azure Repos project, see [Azure Repos](https://azure.microsoft.com/products/devops/repos/).
2828

29-
In this article, you learn how to:
30-
31-
1. [Configure project-level catalogs](#configure-project-level-catalogs)
32-
1. [Configure a managed identity](#configure-a-managed-identity)
33-
1. [Add a catalog from Azure Repos or GitHub](#add-a-catalog)
34-
1. [Update a catalog](#update-a-catalog)
35-
1. [Delete a catalog](#delete-a-catalog)
36-
1. [Troubleshoot catalog sync errors](#troubleshoot-catalog-sync-errors)
37-
3829
## Configure project-level catalogs
3930

4031
Attaching catalogs at the project level enables platform engineers to provide image definitions that are specific to each development teams. Additionally, it empowers dev team leads assigned as Project Admins to manage the image definitions made available to their teams.

0 commit comments

Comments
 (0)