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

pulumi org webhook ping | CLI commands

Generated for Pulumi CLI v3.245.0.

    [EXPERIMENTAL] Send a test ping to an organization webhook

    Synopsis

    [EXPERIMENTAL] Send a test ping to an organization webhook.

    Issues a test ping event to the specified webhook to verify it is properly configured and reachable. Returns the delivery result including the HTTP response code and duration.

    pulumi org webhook ping <id> [flags]
    

    Examples

      # Ping a webhook
      pulumi org webhook ping 1a2b3c4d
    
      # Ping and get full delivery details as JSON
      pulumi org webhook ping 1a2b3c4d --output json
    

    Options

      -h, --help            help for ping
          --org string      The organization that owns the webhook. Defaults to the current org.
          --output string   Output format. Supported values are: default and json (default "default")
    

    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