Flux for swamp: HelmReleases, Kustomizations and sources as three model types, read with kubectl and driven with the flux CLI; and a directory pushed as an OCI artifact for an OCIRepository to pull.
A fork of @ginger_pappa/flux 2026.06.09.1 (MIT, copyright ginger_pappa) merged with the reset method this package used to add to it, so one package owns the types and nothing is pulled from another collective. helmrelease lists releases with chart, requested and applied versions, readiness and source, and reconciles, suspends and resumes one; kustomization does the same for Kustomizations with path, prune and the applied and attempted revisions; source lists GitRepository, HelmRepository and OCIRepository objects with URL, reference and artifact revision, skipping a kind whose CRD is not installed.
get reads one HelmRelease in full, so a caller no longer parses the Ready message: every Helm history entry Flux keeps with revision number, status, chart and app version, deploy times, digests and test hook results; whether the last action was an install or an upgrade and whether it succeeded, taken from structured status fields and condition reasons; the failure counters; the attempted and the applied revision; and the Jobs labelled for the release with their hook types and results. A failed or never installed release is recorded, not thrown, and missing hook Jobs are a recorded fact.
reset is the recovery action the base type lacked: a reconcile with --reset that clears a HelmRelease's failure counters so helm-controller tries again after RetriesExceeded, then reads the object back and records readiness, the newest Helm history status and both counters, so the outcome is a record and not a log line. Two live pre-flight checks confirm flux and kubectl can be run before anything starts, so a missing binary is a named refusal instead of a spawn error part-way through.
push_artifact on the source type is the producer side of an OCIRepository: a directory pushed with flux push artifact, reproducibly, with the source and revision Flux shows on the object that pulls it, OCI annotations, and an optional metadata object written as release.json into a copy of the directory first, so the directory itself is untouched. The record holds the reference by digest and the digest flux printed, so what is signed, promoted or verified afterwards is the artifact as pushed.
Changes from upstream: kubectl output that is not JSON is a named error; a HelmRelease declared through chartRef reports that as its source; the spec is read defensively; every kubectl resource is named by its full group; a name or namespace that is not a Kubernetes name is refused before a command runs; every flux and kubectl process has a time limit and is stopped when a run is cancelled; error text is one bounded line with credentials blanked. flux and kubectl are run by name from PATH and the model's namespace, kubeconfig and context are honoured, as upstream did.