pulumi state protect

protect resource in a stack’s state

Synopsis

Protect resource in a stack’s state

This command sets the ‘protect’ bit on one or more resources, preventing those resources from being deleted.

Caution: this command is a low-level operation that directly modifies your stack’s state. Setting the ‘protect’ bit on a resource in your stack’s state is not sufficient to protect it in all cases. If your program does not also set the ‘protect’ resource option, Pulumi will unprotect the resource the next time your program runs (e.g. as part of a pulumi up).

See https://www.pulumi.com/docs/iac/concepts/options/protect/ for more information on the ‘protect’ resource option and how it can be used to protect resources in your program.

To unprotect a resource, use pulumi unprotecton the resource URN.

To see the list of URNs in a stack, use pulumi stack --show-urns.

pulumi state protect [resource URN] [flags]

Options

      --all            Protect all resources in the checkpoint
  -h, --help           help for protect
  -s, --stack string   The name of the stack to operate on. Defaults to the current stack
  -y, --yes            Skip confirmation prompts

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

• pulumi state - Edit the current stack’s state

Auto generated by spf13/cobra on 8-May-2025