collector: derive the collector maps from one registration table (#2730)

Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>
2026-10-23 21:19:05 +02:00 · 2026-10-15 21:19:47 +00:00
parent b914dbbf6e
commit 379b1553bd
10 changed files with 805 additions and 231 deletions
@@ -143,7 +143,11 @@ exercised a live Windows role.
 - Keep CLI and YAML validation consistent. Reject unknown fields, unsupported
  sub-collector names and invalid values; preserve CLI precedence and repeated
  flag/list behavior. Changes to config shapes also need schema, flag parsing
-  and documentation updates.
+  and documentation updates. A collector is registered once, in the
+  `registrations` table of `pkg/collector/map.go`, with a `Config` field whose
+  YAML key is the collector name and a `docs/collector.<name>.md`;
+  `TestRegistrations` checks that they agree. The configuration file schema in
+  `internal/config` only checks keys: the flags parse and validate the values.
 - For textfiles, keep HELP/type metadata consistent across files and preserve
  unrelated valid series when reporting duplicates or parse failures. Publish
  producer output by replacing a temporary file in the same directory. File