📄️ Bulk catalog ingestion
Bulk catalog ingestion is a guided workflow for onboarding multiple repositories into your Portal catalog at once. It supports multiple source control providers (GitHub, GitLab, Azure DevOps) and offers two management modes: Portal-managed or YAML-managed components. You can choose the management mode for each ingestion batch.
📄️ Understanding Management Modes
When using bulk catalog ingestion, you choose how component metadata will be managed for each ingestion batch. This affects how you update component information, where data is stored, and your team's workflow.
📄️ Portal Mode Walkthrough
You've selected Managed by Portal mode. Here's what happens next as you complete the remaining steps.
📄️ YAML Mode Walkthrough
You've selected Managed by YAML mode. Here's what happens next as you complete the remaining steps.
📄️ Updating Components
After ingesting components into your catalog, you'll need to keep their metadata up to date. Portal provides two editing interfaces for updating component information.
📄️ Enriching Components
Enrichment automatically populates missing metadata on your Portal-managed components by inferring values from your source control provider. It can detect fields like owner, lifecycle, type, and tags — saving you from manually filling in details across many components.
📄️ Troubleshooting
This guide covers common issues you might encounter when using bulk catalog ingestion and how to resolve them.
📄️ FAQ
Can I switch between Portal and YAML management modes later?