Doppler Plugin
Install
pnpm add -D @theholocron/holocron-plugin-doppler
Capabilities
| Capability | Token |
|---|---|
vault | HOLOCRON_DOPPLER_TOKEN (doppler) |
Config
Section titled “Config”providers: { vault: ["doppler", { // Required: Doppler project name project: "my-project", // Required: Doppler config name (e.g. "dev", "stg", "prd") config: "prd", }],}Options
Section titled “Options”| Option | Required | Description |
|---|---|---|
project |
Yes | Doppler project name |
config |
Yes | Doppler config/environment name |
Authentication
Section titled “Authentication”- Go to dashboard.doppler.com and open your project
- Select the config you want to read from (e.g.
prd) - Click Access → Service Tokens → Generate Service Token
- Copy the token — it starts with
dp.st.
holocron auth set doppler dp.st.xxxOr via env var:
export HOLOCRON_DOPPLER_TOKEN=dp.st.xxxWhat vault provides
Section titled “What vault provides”read(key)— reads a single secret by name from the configured project + configwrite(key, value)— sets or updates a secretlist()— lists all secret names in the configenvironments?()— lists all configs in the project ("dev","stg","prd")readEnvironment?(config)— reads all KEY=VALUE pairs from a config (powersholocron secrets sync)ensureProject?(name)— creates a Doppler project if missingensureEnvironment?(project, name)— creates a config (branch) inside a project
Example: sync Doppler → GitHub + Vercel
Section titled “Example: sync Doppler → GitHub + Vercel”# 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