You’ve selected Managed by Portal mode. Here’s what happens next as you complete the remaining steps.Documentation Index
Fetch the complete documentation index at: https://backstage.spotify.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Step 4: Select Repositories
Choose the repositories you want to turn into components. In Portal mode:- Each repository becomes exactly one component (1:1 mapping)
- Any existing
catalog-info.yamlfiles are ignored - Portal will attempt to detect metadata from the repository
Portal shows all repositories from the organizations you selected in Step 3, regardless of whether they have a catalog-info.yaml file.
Step 5: Fill Missing Details (Optional)
Portal auto-detects what it can from your repositories, but some information may be missing. This step is optional. You can:- Fill in details now for complete metadata
- Skip and update later through the Portal UI
Step 6: Review and Complete
Review your selected components before finalizing. This screen shows:- All components that will be created
- Their metadata (name, owner, lifecycle, type)
- Any warnings or missing information
What Happens Next
When you complete the workflow:- Components are immediately registered in the catalog
- They appear in Portal within 1-2 minutes
- All metadata is stored in Portal’s database
- Find your components in the catalog
- Update metadata using the edit and bulk edit dialogs
Managing Your Components
Since these components are managed by Portal:- Updates are made using the edit and bulk edit dialogs, not by editing files
- Metadata lives in Portal’s database, not in your repositories
- No
catalog-info.yamlfiles will be created or used