fluxcd-flux2/cmd/flux/testdata/get
3uzbcqje 5afd1d8728
cmd: support type!=status in get --status-selector
`flux get --status-selector` only supported equality (`type=status`),
so finding objects that are not in a given state required multiple
invocations, e.g. listing everything that is not ready needed both
`Ready=False` and `Ready=Unknown`.

Add support for a negated selector `type!=status`. Since all resource
adapters delegate matching to the shared `statusMatches` helper and
filtering is centralised in `getRowsToPrint`, negation is implemented
purely in the parse/filter layer by inverting the match result. This
covers every resource type and the `--watch` path without touching the
per-resource adapters.

A missing condition is treated as not-matching by `statusMatches` (Flux
considers it "waiting to be reconciled"), so `Ready!=True` also surfaces
objects that have no Ready condition yet, i.e. the complete not-ready set:

    flux get all -A --status-selector Ready!=True

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: 3uzbcqje <3uzbcqje@addy.to>
2026-06-24 10:53:37 -07:00
..
get.golden Add label selector flag to get cmd 2023-04-11 17:00:57 +01:00
get_label_one.golden Add label selector flag to get cmd 2023-04-11 17:00:57 +01:00
get_label_two.golden Add label selector flag to get cmd 2023-04-11 17:00:57 +01:00
get_status_ready_false.golden cmd: support type!=status in get --status-selector 2026-06-24 10:53:37 -07:00
get_status_ready_not_true.golden cmd: support type!=status in get --status-selector 2026-06-24 10:53:37 -07:00
get_status_ready_true.golden cmd: support type!=status in get --status-selector 2026-06-24 10:53:37 -07:00
objects.yaml Update toolkit components 2025-09-15 17:33:20 +01:00
status_objects.yaml cmd: support type!=status in get --status-selector 2026-06-24 10:53:37 -07:00