pulumi stack rename

Rename an existing stack

Synopsis

Rename an existing stack.

Note: Because renaming a stack will change the value of getStack() inside a Pulumi program, if this name is used as part of a resource’s name, the next pulumi up will want to delete the old resource and create a new copy. For now, if you don’t want these changes to be applied, you should rename your stack back to its previous name.

pulumi stack rename <new-stack-name> [flags]

Options

  -h, --help   help for rename

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 (default true)
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --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
  -i, --show-ids                     Display each resource's provider-assigned unique ID
      --show-secrets                 Display stack outputs which are marked as secret in plaintext
  -u, --show-urns                    Display each resource's Pulumi-assigned globally unique URN
  -s, --stack string                 The name of the stack to operate on. Defaults to the current stack
      --tracing string               Emit tracing to a Zipkin-compatible tracing endpoint
  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose

SEE ALSO

Auto generated by spf13/cobra on 22-May-2019