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

pulumi org webhook remove | CLI commands

Generated for Pulumi CLI v3.245.0.

    [EXPERIMENTAL] Delete an organization webhook

    Synopsis

    [EXPERIMENTAL] Delete an organization webhook.

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

    Returns an error if the webhook does not exist.

    pulumi org webhook remove <id> [flags]
    

    Examples

      # Remove a webhook (will prompt for confirmation)
      pulumi org webhook remove 1a2b3c4d
    
      # Remove without confirmation
      pulumi org webhook remove 1a2b3c4d --yes
    

    Options

      -h, --help         help for remove
          --org string   The organization that owns the webhook. Defaults to the current org.
      -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