Let a requirement be optional, binding only a provider that already runs (hq issue 166, ADR 0330)

Making every soft dependency a provision made it hard: a mesh without influxdb could not assign grafana, and one with influxdb in its catalogue would install it for grafana. A requirement may now be written {"name": ..., "optional": true}. It resolves as a hard one when a provider is assigned or reachable, and is otherwise absent: never refused, nothing installed for it. Its binding, credential and only-when-bound files are left out, its ${bound:...|default:...} placeholders take their defaults, the module check refuses one that could render empty, and plan and node list it unbound.
2026-10-13 01:53:18 +02:00
parent 454a3db69a
commit 6ec4139871
12 changed files with 765 additions and 28 deletions
@@ -38,3 +38,4 @@
 ./cmd/mesh-controller TestReplay201ThePlansSend
 ./internal/inventory TestAWalksRestIsReadFromEachMachinesOwnSend
 ./internal/inventory TestAStoredBuildWithASilentMergeableFileIsStillReadAndComposed
+./cmd/mesh-controller TestPlanAndNodeListAnOptionalRequirementLeftUnbound