Repositories
Knowledge Hub is an Early Access release. Refer to the Early Access disclaimer for details.
A repository is the top-level storage container in Knowledge Hub. It holds one or more Knowledge Bases and controls the infrastructure on which vector data is stored.
Managed repositories
In Early Access, Knowledge Hub provides managed repositories only. When you create a repository, Boomi provisions and manages the underlying vector store (OpenSearch) on your behalf. You do not configure or maintain the storage infrastructure.
Customer-owned repositories, where you provide your own vector store, are planned for a future release.
What a repository controls
A repository establishes:
- Storage isolation: Knowledge Bases in different repositories are stored independently. Data from one repository does not appear in queries against another.
- Infrastructure settings: The vector store type (OpenSearch in Early Access) and its configuration are set at the repository level and apply to all Knowledge Bases within it.
- Governance boundary: Repository-level state affects all Knowledge Bases inside it. Disabling or deleting a repository affects all its Knowledge Bases.
Why you might use multiple repositories
You can create more than one repository to separate data along organizational or compliance lines:
- Department separation: A repository for HR data and a separate one for engineering data ensures HR content never appears in engineering agent results.
- Compliance and data residency: If different data sets have different regulatory requirements, keeping them in separate repositories makes it easier to apply controls independently.
- Environment isolation: Separate repositories for development, staging, and production prevent test data from mixing with production content.
Repository states
| State | Meaning |
|---|---|
| Enabled | The repository is active. Knowledge Bases can be created, ingestion can run, and retrieval queries are served. |
| Disabled | The repository is paused. No new ingestion runs. Existing data is retained. Retrieval queries are not served. |
Archiving is not currently supported for repositories. Delete is the only way to permanently remove one. Refer to Asset states reference for allowed state transitions.
Relationship to Knowledge Bases
A repository is a container. All Knowledge Bases must belong to a repository, and each Knowledge Base belongs to exactly one repository. You cannot move a Knowledge Base from one repository to another after it is created.
Next steps
- Refer to Creating a repository to create your first repository.
- Refer to Managing repository lifecycle to disable, enable, or delete a repository.
- Refer to Knowledge bases to learn about the entity repositories contain.
