Fork me on GitHub

pulumi destroy

Destroy an existing stack and its resources


Destroy an existing stack and its resources

This command deletes an entire existing stack by name. The current state is loaded from the associated snapshot file in the workspace. After running to completion, all of this stack’s resources and associated state will be gone.

Warning: although old snapshots can be used to recreate a stack, this command is generally irreversible and should be used with great care.

pulumi destroy [flags]


      --analyzer stringSlice     Run one or more analyzers as part of this update
  -d, --debug                    Print detailed debugging output during resource operations
      --diff                     Display operation as a rich diff showing the overall change
  -h, --help                     help for destroy
  -m, --message string           Optional message to associate with the destroy operation
      --non-interactive          Disable interactive mode
  -p, --parallel int             Allow P resource operations to run in parallel at once (<=1 for no parallelism) (default 10)
  -r, --refresh                  Refresh the state of the stack's resources before this update
      --show-config              Show configuration keys and variables
      --show-replacement-steps   Show detailed resource replacement creates and deletes instead of a single step
      --show-sames               Show resources that don't need to be updated because they haven't changed, alongside those that do
      --skip-preview             Do not perform a preview before performing the destroy
  -s, --stack string             The name of the stack to operate on. Defaults to the current stack
  -y, --yes                      Automatically approve and perform the destroy after previewing it

Options inherited from parent commands

      --color colors.Colorization    Colorize output. Choices are: always, never, raw, auto (default always)
  -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
      --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
      --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


Auto generated by spf13/cobra on 16-Oct-2018