doppler

Setup Doppler CLI in the current directory

$ doppler setup

$ doppler setup

$ doppler run --command [command]

$ doppler projects

$ doppler secrets

$ doppler open

doppler [OPTIONS] COMMAND [ARGS...]

--help
    Displays help information for the doppler command or a specific subcommand.

--version
    Prints the current version of the Doppler CLI.

--json
    Outputs command results in JSON format, suitable for programmatic parsing.

--project <name|id>
    Specifies the Doppler project to operate on, overriding the default or configured project.

--config <name|id>
    Specifies the Doppler config (environment) to operate on, overriding the default or configured config.

--scope <scope>
    Defines the scope for certain commands, e.g., 'project' or 'config'.

--token <token>
    Provides a service token for authentication, typically used in non-interactive environments.

--cwd <path>
    Sets the current working directory for the command execution.

--no-check-update
    Disables automatic checks for new CLI updates.

The doppler command is the official command-line interface (CLI) for the Doppler platform, a centralized system for managing secrets, environment variables, and configurations. It allows developers and operations teams to securely synchronize, inject, and access sensitive data across various environments, from local development to production. The CLI provides functionality to authenticate with the Doppler service, download and manage secrets, and execute applications with secrets injected directly into their environment. It integrates seamlessly into CI/CD pipelines, offering versioning, access control, and auditing capabilities for all secrets.

The doppler command requires an active Doppler account and network connectivity to the Doppler platform for most of its functionality.
Authentication via doppler login or a valid service token is necessary to access and manage secrets.
It is not a standalone utility for local secret storage; it relies on the cloud-based Doppler service.

The doppler command's primary functionality is exposed through a rich set of subcommands, each designed for specific tasks. Users typically interact with these subcommands rather than the top-level command directly. Examples include:
doppler login: Authenticates the CLI with your Doppler account.
doppler secrets download: Downloads secrets from a specified config.
doppler run: Executes a command with secrets injected into its environment.
doppler configure: Manages local project and config settings.
doppler projects: Manages Doppler projects.
doppler configs: Manages Doppler configurations (environments).

For interactive use, authentication is typically handled via doppler login, which opens a browser for OAuth-based login. For CI/CD environments or automated scripts, service tokens or configuration files are used to authenticate the CLI.

Doppler emerged as a modern solution to address the growing complexity of secrets management in cloud-native and microservices architectures. Its development has focused on providing a secure, auditable, and developer-friendly way to handle sensitive configurations, moving beyond traditional environment variables and insecure file storage. The CLI has evolved with features like dynamic secret injection and broad integration capabilities, reflecting the needs of contemporary DevOps practices.