3.1 Populating the Component Catalog
PHASE OBJECTIVE
Configure and populate compass ahead of inviting users to the platform.
3.1 Populating the component catalog
The component catalog is the foundation of Compass, populating it is the first step in establishing your new internal developer platform. Below are the methods available to populate the catalog.
3.1.1 Connecting to a Source Code Repository (most preferred)
Connecting your organization's source code repository tool with Compass is the most efficient path to a populated platform. Connecting your source code repository provides Compass with a rich data set, including:
- Populating the component catalog, mapping each repository to a component
- Populating the activity feed with deployment details
- Populates default metrics such as Deployment Frequency, Build Time, and Pull Request Cycle time
Connecting some source code repositories to Compass enable config-as-code for the management of components.
3.1.2 Import Components from New Relic
If your team uses New Relic for application performance monitoring (APM), you can import your monitored services directly into Compass. Connecting your Compass instance with New Relic is an easy way to start populating your Compass component catalog.
3.1.3 Creating components via API or a CSV file
Compass components can be created using the API or a CSV file, depending on your scenario.