1. Docs
  2. Pulumi CLI
  3. Commands
  4. pulumi env diff

pulumi env diff

    Show changes between versions.

    Synopsis

    Show changes between versions

    This command displays the changes between two environments or two versions of a single environment.

    The first argument is the base environment for the diff and the second argument is the comparison environment. If the environment name portion of the second argument is omitted, the name of the base environment is used. If the version portion of the second argument is omitted, the ’latest’ tag is used.

    pulumi env diff [<org-name>/]<environment-name>[@<version>] [[[org-name/]<environment-name>]@<version>] [flags]
    

    Options

      -f, --format string   the output format to use. May be 'dotenv', 'json', 'yaml', 'detailed', or 'shell'
      -h, --help            help for diff
          --path string     Show the diff for a specific path
          --show-secrets    Show static secrets in plaintext rather than ciphertext
    

    Options inherited from parent commands

          --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
      -C, --cwd string                   Run pulumi as if it had been started in another directory
          --disable-integrity-checking   Disable integrity checking of checkpoint files
      -e, --emoji                        Enable emojis in the output
          --env string                   The name of the environment to operate on.
      -Q, --fully-qualify-stack-names    Show fully-qualified stack names
          --logflow                      Flow log settings to child processes (like plugins)
          --logtostderr                  Log to stderr instead of to files
          --memprofilerate int           Enable more precise (and expensive) memory allocation profiles by setting runtime.MemProfileRate
          --non-interactive              Disable interactive mode for all commands
          --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
          --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
      -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose
    

    SEE ALSO

    Auto generated by spf13/cobra on 13-Jun-2024
      Introducing Pulumi Copilot - Intelligent Cloud Management