pulumi stack webhook delivery redeliver | CLI commands

[EXPERIMENTAL] Redeliver a specific webhook event

Synopsis

[EXPERIMENTAL] Redeliver a specific webhook event.

Triggers the Pulumi Service to redeliver a specific event to a webhook. This is useful for resending an event that the webhook endpoint failed to process on the initial delivery attempt.

Returns the delivery result with HTTP status and response details. Returns an error if the webhook or event does not exist.

pulumi stack webhook delivery redeliver <webhook> <event-id> [flags]

Examples

  # Redeliver an event
  pulumi stack webhook delivery redeliver my-webhook evt-abc123

  # Redeliver and get the full result as JSON
  pulumi stack webhook delivery redeliver my-webhook evt-abc123 --output json

Options

  -h, --help            help for redeliver
  -o, --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 delivery - [EXPERIMENTAL] Inspect stack webhook deliveries