Overview
A Dependency Repository is a tenant-level object in Yeedu that points at an object-storage bucket holding the dependency artifacts your workloads need: JARs, packages, archives and similar files.
Each dependency repository is simply a named pairing of:
- a cloud provider,
- a credential registered for that provider, and
- a bucket name.
Once created, the repository can be attached to a cluster, so that the cluster resolves its dependencies from that bucket using the stored credential instead of requiring every job or notebook to carry its own storage credentials.
Why Dependency Repositories Exist
- Centralised artifacts : one bucket of shared JARs, packages and archives, defined once per tenant rather than per cluster or per job.
- Credential reuse : the bucket is accessed through an existing Yeedu credential, so storage keys are never repeated in cluster or job configuration.
- Tenant-wide scope : dependency repositories live alongside Clusters, Secrets and Metastores at the tenant level, so every workspace in the tenant can use them.
Where It Appears in Yeedu
Tenant navigation
Dependency Repositories is a first-class item in the tenant left navigation, between Secrets and Metastores:
Workspaces | Clusters | Access Management | Secrets | Dependency Repositories | Metastores | Usage
It opens the dependency repository list page at /tenant/<tenant-id>/dependency-management.
Create Cluster form
On the Create Cluster form, Dependency Repository is a top-level, optional field rendered between Acceleration and Run Time Version. It's a clearable dropdown with an inline + button that opens the create-repository flow without leaving the cluster form.
See Create Dependency Repository for the fields on that flow.
Supported Cloud Providers
| Cloud Provider | Available on the Dependency Repository form |
|---|---|
| OnPrem | Yes |
| GCP | Yes |
| AWS | Yes |
| Azure | Yes |
| OCI | No |
We support OCI as a cloud provider elsewhere in the product. The Create Cloud Environment form and the Cloud Providers filter on the Usage dashboard both list OCI alongside OnPrem, GCP, AWS and Azure.
The Cloud Provider dropdown on the Create Dependency Repository form does not include OCI. If your workload runs on an OCI cloud environment, you can't currently back it with an OCI-hosted dependency repository from this form.