pulumi stack webhook edit | CLI commands

[EXPERIMENTAL] Update a stack webhook’s configuration

Synopsis

[EXPERIMENTAL] Update a stack webhook’s configuration.

Modifies an existing webhook. Only the flags you pass are changed; all other fields are preserved. For example, passing –active=false disables the webhook without altering its URL or filters.

To clear the webhook secret, pass –secret “”.

Returns an error if the webhook does not exist.

pulumi stack webhook edit <name> [flags]

Examples

  # Disable a webhook
  pulumi stack webhook edit my-hook --active=false

  # Change the payload URL
  pulumi stack webhook edit my-hook --url https://new-url.example.com

  # Add event filters
  pulumi stack webhook edit my-hook --add-event update_succeeded --add-event update_failed

  # Remove an event and add another
  pulumi stack webhook edit my-hook --remove-event update_failed --add-event destroy_failed

  # Clear the secret
  pulumi stack webhook edit my-hook --secret ""

Options

      --active                     Whether the webhook is active (default true)
      --add-event stringArray      An event type to add (repeatable)
      --add-group stringArray      An event group to add (repeatable)
      --display-name string        The webhook display name
  -h, --help                       help for edit
      --hook-format string         The webhook format: raw, slack, ms_teams, or pulumi_deployments
  -o, --output string              The output format: default (human-readable text) or json (default "default")
      --remove-event stringArray   An event type to remove (repeatable)
      --remove-group stringArray   An event group to remove (repeatable)
      --secret string              The HMAC key for signature verification (empty string removes the secret)
  -s, --stack string               The name of the stack to operate on. Defaults to the current stack
      --url string                 The webhook payload URL

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