pulumi stack webhook ping | CLI commands

[EXPERIMENTAL] Send a test ping to a stack webhook

Synopsis

[EXPERIMENTAL] Send a test ping to a stack webhook.

Issues a test ping event to the specified webhook to verify it is properly configured and reachable. Unlike normal webhook deliveries, this bypasses the message queue and sends the request directly to the webhook endpoint.

The response includes the full delivery result: the HTTP request URL, response status code, response body, and request duration.

Returns an error if the webhook does not exist.

pulumi stack webhook ping <name> [flags]

Examples

  # Ping a webhook to verify it works
  pulumi stack webhook ping my-webhook

  # Ping a webhook and get the full delivery details as JSON
  pulumi stack webhook ping my-webhook --output json

Options

  -h, --help            help for ping
      --output string   The output format: default (human-readable text) or json (default "default")
  -s, --stack string    The name of the stack to operate on. Defaults to the current stack

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

• pulumi stack webhook - [EXPERIMENTAL] Manage stack webhooks