← docs

dotenv-vault versions

Written by Mot

List version history for your project in dotenv-vault.

1

Run versions command

$ npx dotenv-vault versions
remote:   Listing versions... done
Ver    Change                                                                By                           When
────── ───────────────────────────────────────────────────────────────────── ────────────────────── ────────────────────
v35    AIRBRAKE_API_KEY,STRIPE_API_KEY,LOCKBOX_MASTER_KEY,SECRET_S3          ana.kennedy@dotenv.org 2022-05-04T19:25:56Z
v33    SECRET_S3                                                             ana.kennedy@dotenv.org 2022-03-14T07:35:42Z
v31    STRIPE_API_KEY                                                        ana.kennedy@dotenv.org 2022-03-14T07:34:05Z
v30    S3_KEY                                                                ana.kennedy@dotenv.org 2022-03-14T07:33:51Z
v29    AIRBRAKE_API_KEY                                                      ana.kennedy@dotenv.org 2022-03-14T07:33:13Z
v28    S3_KEY                                                                ana.kennedy@dotenv.org 2022-03-14T07:32:10Z
v27    AIRBRAKE_PROJECT_ID,AIRBRAKE_API_KEY,STRIPE_API_KEY,GIVEBRIGHTER_HOST ana.kennedy@dotenv.org 2022-03-14T07:32:09Z
v26    STRIPE_API_KEY                                                        ana.kennedy@dotenv.org 2022-03-14T07:30:31Z
...
Pull a version with npx dotenv-vault pull development@v35

That's it!


More information

For more information on the versions command, run dotenv-vault help versions.

$ npx dotenv-vault help versions
List version history

USAGE
  $ dotenv-vault versions [ENVIRONMENT] [-m ] [-y]

ARGUMENTS
  ENVIRONMENT  Set environment to check versions against. Defaults to development

FLAGS
  -m, --dotenvMe=         Pass .env.me (DOTENV_ME) credential directly (rather than reading from .env.me file)
  -y, --yes               Automatic yes to prompts. Assume yes to all prompts and run non-interactively.

DESCRIPTION
  List version history

EXAMPLES
  $ dotenv-vault versions
ARGUMENTS

[ENVIRONMENT]

Set environment to check versions against. Defaults to development

$ npx dotenv-vault versions production
remote:   Listing production versions... done
Ver    Change                  By                           When
────── ─────────────────────── ────────────────────── ────────────────────
v31    SECRET_S3                                      2022-03-14T07:35:29Z
v30    S3_KEY                                         2022-03-14T07:32:10Z
v29    STRIPE_API_KEY          ana.kennedy@dotenv.org 2021-11-23T15:20:35Z
v28    STRIPE_API_KEY          ana.kennedy@dotenv.org 2021-11-09T15:56:21Z
v27    AIRBRAKE_PROJECT_ID     ana.kennedy@dotenv.org 2021-11-09T15:53:08Z
v26    AIRBRAKE_API_KEY        ana.kennedy@dotenv.org 2021-11-09T15:53:00Z
...

FLAGS

-m, --dotenvMe

Pass .env.me (DOTENV_ME) credential directly (rather than reading from .env.me file)

$ npx dotenv-vault versions --dotenvMe=me_b1831e…
# use credential set from dotenvMe rather than .env.me file

-y, --yes

Automatic yes to prompts. Assume yes to all prompts and run non-interactively.

$ npx dotenv-vault versions -y
# skips over prompt for permission to open browser window

Next command(s).