Skip to content

Guides

End-to-end workflows for the most common OpenDepot use cases.

For Users

Guides for teams consuming modules and providers from OpenDepot.

  •  Consuming Modules

    Reference synced modules from your OpenTofu or Terraform configurations using the registry source format.

  •  Consuming Providers

    Use OpenDepot as a private provider mirror, including GPG-verified downloads for air-gapped environments.

For Admins

Guides for platform and infrastructure teams operating OpenDepot.

  •  GitOps with Argo CD

    Manage Module manifests in Git and let Argo CD sync them to the cluster. Every published version maps to an approved, merged pull request.

  •  Depot (Pull-Based)

    Automatically discover and sync module and provider versions from GitHub and HashiCorp without writing any kubectl apply commands or configuring direct pipeline authentication.

  •  CI/CD Pipelines

    Pipeline-focused workflows for CI/CD registry reads (OIDC or token-based auth) and push-based publishing of Module resources.

  •  Registry Operations

    Day-2 admin runbooks for force re-sync, module/provider lifecycle operations, scanning checks, and pre-signed URL tuning.

  •  Migrating to OpenDepot

    Move existing modules and providers from the public registry or another self-hosted registry to OpenDepot.

  •  GroupBinding Access Control

    Restrict which modules and providers each OIDC group may access using GroupBinding resources and expr-lang expressions.

  •  Registry Explorer UI

    Enable the browsable registry frontend, configure public visibility labels, and set up OIDC login and GroupBinding-based access for the UI.