doppler-projects

Get all projects

$ doppler projects

$ doppler projects get [name|project_id]

$ doppler projects create [name]

$ doppler projects update [name|project_id] --name "[new_name]" --description "[new_description]"

$ doppler projects delete [name|project_id]

doppler projects <command> [options]

Examples:
doppler projects list
doppler projects create --name my-new-project --description "A project for my application"
doppler projects delete --project old-project --confirm

--json
    Outputs the command result in JSON format. This option is available across many doppler subcommands for programmatic parsing.

--name <name>
    Specifies the name of the project. Required when creating a new project (doppler projects create) or providing a new name when updating (doppler projects update).

--description <description>
    Provides a textual description for the project. Optional when creating a new project (doppler projects create) or updating an existing one (doppler projects update).

--project <project_name>
    Identifies the target project for operations such as deletion (doppler projects delete) or updating (doppler projects update). Use the exact name of the project.

--confirm
    Bypasses the interactive confirmation prompt, typically used for destructive actions like deleting a project (doppler projects delete), making it suitable for scripting.

The doppler projects command group, part of the Doppler CLI, enables comprehensive management of Doppler projects directly from the terminal. Projects serve as the primary organizational units within Doppler for grouping secrets and configurations across different environments (e.g., development, staging, production). This command group provides functionalities to list existing projects, create new ones, delete projects, and update their details. It is an indispensable tool for developers and operations teams seeking to integrate secrets management into their automated workflows, scripting, and continuous delivery pipelines, ensuring secure and consistent application environments.

Key Considerations:
doppler projects requires the Doppler CLI to be installed and properly authenticated against your Doppler workspace.
User permissions within Doppler must be configured to allow project management operations (e.g., creating, deleting, or updating projects).
Deleting a project is an irreversible action that permanently removes all associated environments, configurations, and secrets. Exercise caution when using the delete subcommand.
The CLI may prompt for interactive input unless specific options like --confirm are used for scripting.

The primary subcommands within doppler projects are:
list: Displays all projects accessible to the current user.
create: Establishes a new project with a specified name and optional description.
delete: Permanently removes an existing project and all its associated data.
update: Modifies the name or description of an existing project.

In Doppler's architecture, projects are the highest level of organization. Each project can contain multiple environments (e.g., 'dev', 'staging', 'prod'), and each environment can hold various configurations, which in turn store your actual secrets.

The doppler projects subcommand group is an integral part of the Doppler Command Line Interface (CLI), which was developed to extend the functionality of the Doppler secrets management platform beyond its web-based user interface. Its introduction provided developers and operations teams with programmatic control over their projects, enabling seamless integration into automated workflows, CI/CD pipelines, and infrastructure as code practices. This CLI functionality has continuously evolved alongside the Doppler platform, enhancing its capabilities for scalable and secure secret management.

doppler(1), doppler configs(1), doppler secrets(1), doppler setup(1)