Create Dependency Repository
Overview
Creating a dependency repository registers a storage bucket with Yeedu so that clusters can resolve their dependency artifacts from it. The registration is small, five fields in all, but it ties three things together: a cloud provider chosen from OnPrem, GCP, AWS or Azure, a credential already registered for that provider, and the name of the bucket holding the artifacts. Description is the only one of the five you can leave blank.
The form is reached at:
/tenant/<tenant-id>/dependency-management/create-dependency
Breadcrumb: Dependency Repository > New Repository
You can also reach the same flow from the + button next to the Dependency Repository dropdown on the Create Cluster form.
Steps
- In the tenant left navigation, click Dependency Repositories.
- Click + Repository.
- Fill in the fields described below.
- Click Create.
Fields
| Field | Required | Control | Notes |
|---|---|---|---|
| Repository Name | Yes | Text | Placeholder Enter Repository Name. Identifies the repository in the list and in the cluster form dropdown. |
| Description | No | Text | Free-text description of the repository. |
| Cloud Provider | Yes | Dropdown | See Cloud Provider options. Determines which credentials are offered in the next field. |
| Credential Name | Yes | Dropdown + inline + | Lists the credentials registered for the selected cloud provider. The + button opens the create-credential flow inline, so you don't have to leave the form to register a new credential. |
| Bucket Name | Yes | Text | Placeholder e.g., my-deps-bucket. The object-storage bucket holding the dependency artifacts. |
Cloud Provider options
The Cloud Provider dropdown offers exactly four values:
| Value | Description |
|---|---|
| OnPrem | On-premises deployment, backed by S3-compatible object storage. |
| GCP | Google Cloud Platform. |
| AWS | Amazon Web Services. |
| Azure | Microsoft Azure. |
Unlike the Create Cloud Environment form, which offers OCI | OnPrem | GCP | AWS | Azure, the Cloud Provider dropdown on this form omits OCI. There's no way to create an OCI-backed dependency repository from this form in v2.10.1.
The on-premises option is labelled OnPrem on this form. Some of our older material refers to the same provider as Proxmox; the label we show in the UI is OnPrem.
Credential Name
The credentials offered depend on the Cloud Provider you selected. The credential types we have seen against existing dependency repositories are:
| Cloud Provider | Credential type |
|---|---|
| OnPrem | Custom S3a Credentials |
| GCP | Google Service Account |
| AWS | AWS Access Secret Key Pair |
| Azure | Azure Service Principal |
If no suitable credential exists yet, use the + button beside the dropdown to create one without leaving the form. The cloud provider of the new credential is fixed to the provider already selected above.
Actions
| Button | Effect |
|---|---|
| Reset | Clears all fields on the form back to their empty state. |
| Create | Validates the form and creates the dependency repository. |
Using the Repository
Once created, the repository becomes selectable in the Dependency Repository dropdown on the Create Cluster form. That field is optional and clearable, so a cluster can be created with no dependency repository attached.