doppler-projects

manage Doppler projects and environments

TLDR

List projects (the bare command lists them; there is no `list` subcommand)

$ doppler projects

Create a project with a description

$ doppler projects create [name] --description "[description]"

Get project info

$ doppler projects get [project_id]

Rename a project or change its description

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

Delete a project without a confirmation prompt

$ doppler projects delete [project_id] --yes

Page through a long project list

$ doppler projects --number [50] --page [2]

SYNOPSIS

doppler projects [subcommand] [projectid] [flags_]

doppler projects manages Doppler projects, the top-level container in the Doppler model. A project holds *environments* (development, staging, production), each of which holds one or more *configs*, and it is the configs that actually store secrets.Projects normally map one-to-one onto an application or service. Because a project is the unit that access control and audit logging hang off, splitting services into separate projects is what lets you grant a team access to one service's secrets without exposing another's.Most day-to-day work happens in `doppler secrets` and `doppler run`; the project subcommands are mainly used at setup time, when onboarding a new service, or from scripts that provision environments automatically.

PARAMETERS

-p, --project NAME

Project to act on, overriding the one configured for this directory.

--name NAME / --description TEXT

Metadata to set on create and update.

-n, --number N

Maximum number of projects to display. Defaults to 100.

--page N

Page of results to display. Defaults to 1.

-y, --yes

Proceed without an interactive confirmation prompt.

--json

Print the result as JSON.

SUBCOMMANDS

(none)

Listing is the default action: running doppler projects with no subcommand prints the projects you can see.

get [projectid_]

Show the details of one project.

create [name]

Create a project. --name and --description may be given as flags instead of positionally.

update [projectid_]

Change a project's --name or --description.

delete [projectid_]

Delete a project and everything in it.

INSTALL

brew install doppler

nix profile install nixpkgs#doppler

CAVEATS

delete removes the project along with every config and secret inside it, and the CLI will only prompt once. Passing --yes removes even that prompt, which makes it easy to destroy a production project from a script. Project names are used as identifiers throughout the CLI and API, so renaming one with update --name can break service tokens, CI configuration, and `doppler setup` state that referred to the old name.

RESOURCES

Source code · Homepage · Documentation