pulumi org webhook list | CLI commands

[EXPERIMENTAL] List all webhooks configured for an organization

Synopsis

[EXPERIMENTAL] List all webhooks configured for an organization.

Returns all webhooks configured at the organization level. Each webhook includes its ID, name, payload URL, format, event groups, events, and active status.

Organization-level webhooks can fire on stack lifecycle events, deployment events, drift detection events, and policy violation events.

pulumi org webhook list [flags]

Examples

  # List webhooks for the default organization
  pulumi org webhook list

  # List webhooks for a specific organization
  pulumi org webhook list --org my-org

  # List webhooks as JSON
  pulumi org webhook list --output json

Options

      --all             Show all results (mutually exclusive with --count)
      --count int       Number of results to display
  -h, --help            help for list
      --org string      The organization to list webhooks for. 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

• pulumi org webhook - [EXPERIMENTAL] Manage organization-level webhooks