Flux CLI introduces flux trigger receiver
Introduced 2026-06-30 · score 0.93
HOW TO USE IT
When debugging a Receiver’s event-driven reconciliation workflow, send its webhook with `flux trigger receiver`, which computes the webhook path and POSTs the payload; it does not require Kubernetes cluster access.
flux trigger receiver <receiver-name> --token=<receiver-token> --url=<webhook-base-url>WHY THIS HELPS
Trigger a Flux receiver while debugging a repository's event-driven reconciliation workflow.
REQUIREMENTS AND LIMITATIONS
- Version: v2.9.0
- <receiver-name> (required): Receiver name used to compute the webhook path.
- --token (required): Receiver token; required for generic and generic-hmac, and must not be set for generic-oidc.
- --url (required): Base URL of the notification-controller webhook receiver; may include a base path.
- --type: Receiver type: `generic`, `generic-hmac`, or `generic-oidc`; defaults to `generic`.
- --payload: JSON request body; defaults to `{}`.
- --oidc-audience: Audience of OIDC token to fetch; requires `--oidc-provider`; defaults to `notification-controller`.
- --oidc-provider: OIDC provider to fetch token from: `github` or `forgejo`; generic-oidc only and mutually exclusive with `--oidc-token`.
- --oidc-token: OIDC token for the request; generic-oidc only, mutually exclusive with `--oidc-provider`; defaults to `FLUX_TRIGGER_RECEIVER_OIDC_TOKEN`.
- --retries: Retry count on connection errors or retryable HTTP status codes (404, 408, 429, 5xx); defaults to 10; `0` disables retries.
- --retry-delay: Delay between retries; defaults to 10s.
- Prerequisite: Use a Flux CLI version that includes the command (introduced in v2.9.0).
- Prerequisite: For generic and generic-hmac, provide the Receiver token; generic-oidc must not set `--token`.
FIRST-PARTY EVIDENCE
- https://github.com/fluxcd/flux2/releases/tag/v2.9.0
- https://v2-9.docs.fluxcd.io/flux/cmd/flux_trigger_receiver/
Check the installed version and the source before using it. Entry JSON