pulumi org webhook new | CLI commands

[EXPERIMENTAL] Create a new organization webhook

Synopsis

[EXPERIMENTAL] Create a new organization webhook.

Creates a webhook that delivers events for the specified organization to a given URL. Organization webhooks can fire on stack lifecycle, deployment, drift detection, environment, and policy violation events.

When run interactively, prompts for required values that aren’t provided via flags. Pass –yes to accept defaults without prompting.

pulumi org webhook new [flags]

Examples

  # Create a webhook interactively
  pulumi org webhook new --name my-hook

  # Create non-interactively
  pulumi org webhook new --name my-hook --url https://example.com/hook --yes

  # Create with specific event groups
  pulumi org webhook new --name my-hook \
    --url https://example.com --group stacks --group deployments --yes

Options

      --active               Whether the webhook is active (default true)
      --event stringArray    An event type to subscribe to (repeatable)
      --group stringArray    An event group to subscribe to (repeatable)
  -h, --help                 help for new
      --hook-format string   The webhook format: raw, slack, or ms_teams (default "raw")
      --name string          The webhook name (1-32 chars, alphanumeric/hyphens/underscores/dots)
      --org string           The organization to create the webhook in. Defaults to the current org.
      --output string        Output format. Supported values are: default and json (default "default")
      --secret string        The HMAC key for signature verification
      --url string           The webhook payload URL, including protocol (e.g. https://example.com/hook)
  -y, --yes                  Skip prompts and proceed with default values

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 org webhook - [EXPERIMENTAL] Manage organization-level webhooks