feat(dns plugin): add --no-managed to list only your own records

[scotwells]

--managed could only answer half the question. It showed the records Datum writes for you, but there was no way to ask the opposite — what did I put here — and in a zone where another system writes most of the records, that is the more useful view.

--no-managed is that view:

• --managed — the records Datum manages for you
• --no-managed — only your own
• absent — everything, unchanged

--managed=false means the same as --no-managed. It already parsed before this filter existed, where it silently meant "no filter", so anyone typing the intuitive thing got the unfiltered list back with no sign their flag had done nothing. Leaving it inert now would be the more surprising choice.

Passing both flags is a usage error rather than a precedence puzzle resolved silently.

In datum-staging.net, where a connector writes 15 of the 19 owner names:

$ datumctl dns record list datum-staging.net --no-managed
NAME                                       TYPE   TTL    VALUE                                    STATUS
_datum-custom-hostname.datum-staging.net   TXT    Auto   "3fd32fac-dfc3-4e97-9041-ca1b31346a1e"   Programmed
ns1                                        A      5m     34.85.246.201                            Programmed
ns2                                        A      5m     34.85.246.201                            Programmed
testing-dns                                A      Auto   1.1.1.1                                  Programmed

That table is ~90 columns. The unfiltered one is 180, because the machine-written names are 69 characters each.

Why this rather than truncating NAME

NAME is an address — record describe|delete <domain> <name> <TYPE> take it as an argument — so shortening it costs you the ability to act on the row, unlike a value, which is never typed. Measured across real zones, a 56-column cap would also cut 59% of one zone's rows while doing nothing at all in another. Removing rows you did not ask about beats damaging the identifiers of rows you did.

Related

Three readability fixes for datumctl dns record list, reviewed and merged bottom-up:

1. fix(dns plugin): shorten long record values in the default table #107 — shorten long values (base: main)
2. feat(dns plugin): add --no-managed to list only your own records #108 — --no-managed to hide records another system writes
3. fix(dns plugin): shorten machine-written names in the default table #109 — shorten machine-written names

All three follow #102, which added the plugin, and are UX fixes found while using it against real staging zones. The plugin ships from #106's release plumbing and is installed via datum-cloud/datumctl-plugins#22.

This alone was not enough for zones where a third party writes the records — Datum does not label those as managed — which is what #109 addresses.