Skip to content
Holocron

Doppler Plugin

@theholocron/holocron-plugin-doppler implements the vault capability against Doppler’s REST API — projects, configs, secrets, plus token verification for holocron auth.

Install

Terminal window
pnpm add -D @theholocron/holocron-plugin-doppler

Capabilities

Capability Token required
vault HOLOCRON_DOPPLER_TOKEN (doppler)

Config

providers: {
  vault: ["doppler", {
    // Required: Doppler project name
    project: "my-project",
    // Required: Doppler config name (e.g. "dev", "stg", "prd")
    config: "prd",
  }],
}

Options

Option Required Description
project Yes Doppler project name
config Yes Doppler config/environment name

Authentication

Terminal window
holocron auth set doppler dp.st.xxx

Or via env var:

Terminal window
export HOLOCRON_DOPPLER_TOKEN=dp.st.xxx

Generate a service token in the Doppler dashboard → Project → Config → Access → Service Tokens.

What vault provides

  • read(key) — reads a single secret by name from the configured project + config
  • write(key, value) — sets or updates a secret
  • list() — lists all secret names in the config
  • environments?() — lists all configs in the project ("dev", "stg", "prd")
  • readEnvironment?(config) — reads all KEY=VALUE pairs from a config (powers holocron secrets sync)
  • ensureProject?(name) — creates a Doppler project if missing
  • ensureEnvironment?(project, name) — creates a config (branch) inside a project

Example: sync Doppler → GitHub + Vercel

Terminal window
# Pull all secrets from the "production" config →
# → set as GitHub Actions secrets
# → set as Vercel env vars (production + preview)
holocron secrets sync production --project-id prj_vercel_xxx