pulumi stack

Manage stacks

Synopsis

Manage stacks

An stack is a named update target, and a single project may have many of them. Each stack has a configuration and update history associated with it, stored in the workspace, in addition to a full checkpoint of the last known good update.

pulumi stack [flags]

Options

  -h, --help           help for stack
  -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

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
      --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
      --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-Nov-2019