pulumi state delete

Deletes a resource from a stack’s state

Synopsis

Deletes a resource from a stack’s state

This command deletes a resource from a stack’s state, as long as it is safe to do so. The resource is specified by its Pulumi URN. If the URN is omitted, this command will prompt for it.

Resources can’t be deleted if other resources depend on it or are parented to it. Protected resources will not be deleted unless specifically requested using the –force flag.

Make sure that URNs are single-quoted to avoid having characters unexpectedly interpreted by the shell.

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

pulumi state delete [resource URN] [flags]

Examples

pulumi state delete 'urn:pulumi:stage::demo::eks:index:Cluster$pulumi:providers:kubernetes::eks-provider'

Options

      --force               Force deletion of protected resources
  -h, --help                help for delete
  -s, --stack string        The name of the stack to operate on. Defaults to the current stack
      --target-dependents   Delete the URN and all its dependents
  -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-Oct-2024