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

pulumi env edit

    Edit an environment definition


    Edit an environment definition

    This command fetches the current definition for the named environment and opens it for editing in an editor. The editor defaults to the value of the VISUAL environment variable. If VISUAL is not set, EDITOR is used. These values are interpreted as commands to which the name of the temporary file used for the environment is appended. If no editor is specified via the –editor flag or environment variables, edit defaults to vi.

    pulumi env edit [<org-name>/]<environment-name> [flags]


          --editor string   the command to use to edit the environment definition
      -f, --file -          the file that contains the updated environment, if any. Pass - to read from standard input.
      -h, --help            help for edit
          --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


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