We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 7 since June 2026, each linked to its source.
fluxWhen bootstrapping Flux from a monorepo, pass `--sparse-checkout` with comma-separated directories and include the directory given to `--path`.
flux bootstrap github --owner=<owner> --repository=<repository> --path=<path> --sparse-checkout=<path>,<directory>When you need a catalog plugin in a Flux repository, search with `flux plugin search`, install it with `flux plugin install <name>`, then invoke it as `flux <name>`. Manage installed plugins with `flux plugin ls`, `flux plugin update [<name>]`, and `flux plugin uninstall <name>`.
flux plugin search [<query>]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>When creating a Receiver webhook secret, run `flux create secret receiver` with a name, receiver type, and webhook hostname. For GCR receivers, also provide the required service account email claim.
flux create secret receiver <name> --namespace=<namespace> --type=github --hostname=<hostname> --exportWhen you need an OCIRepository to select and process a specific OCI layer, run `flux create source oci` with `--layer-selector=<media-type>:<operation>` and `--export` to render the resource YAML.
flux create source oci <name> --url=<oci-url> --tag=<tag> --layer-selector=<media-type>:<operation> --exportWhen inspecting Kustomization or HelmRelease source references, run `flux get ks --show-source` or `flux get hr --show-source`. The flag displays each resource’s source reference.
flux get ks --show-sourceWhen configuring an OIDC-secured webhook Receiver, set its type to `generic-oidc` and define an OIDC provider with validations and the Flux resources to reconcile. The Receiver uses no Secret; callers send a valid OIDC ID token in the `Authorization: Bearer` header.
apiVersion: notification.toolkit.fluxcd.io/v1
kind: Receiver
metadata:
name: <receiver-name>
namespace: <namespace>
spec:
type: generic-oidc
oidcProviders:
- issuerURL: <issuer-url>
validations:
- expression: "<CEL expression>"
message: "<failure message>"
resources:
- apiVersion: <api-group>/<version>
kind: <resource-kind>
name: <resource-name>