Skip to main content
  1. Docs
  2. pulumi stack webhook remove | CLI commands

pulumi stack webhook remove | CLI commands

Generated for Pulumi CLI v3.242.0.

    [EXPERIMENTAL] Delete a stack webhook

    Synopsis

    [EXPERIMENTAL] Delete a stack webhook.

    Permanently removes the specified webhook from the stack. This cannot be undone. You will be prompted to confirm unless –yes is passed.

    Returns an error if the webhook does not exist.

    pulumi stack webhook remove <name> [flags]
    

    Examples

      # Remove a webhook (will prompt for confirmation)
      pulumi stack webhook remove my-webhook
    
      # Remove without confirmation
      pulumi stack webhook remove my-webhook --yes
    

    Options

      -h, --help           help for remove
      -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
          --otel-traces string           Export OpenTelemetry traces to the specified endpoint. Use file:// for local JSON files, grpc:// for remote collectors
          --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