2 Commits

Include renames

Author	SHA1	Message	Date
jklein	6371f60eeb	Guard the four unguarded OnePasswordItem references with required() ... calibre-web-automated 7.0.0, minecraft-server 6.0.0 and urlaubsverwaltung 10.0.0 each majors: an installation that renders today with an empty itemPath stops rendering. searxng 1.0.6 is documentation only - its valkey reference is correctly optional and stays gated by {{- if }}. Every message names the values path. values.yaml now says per key why it is required, reusing the wording the charts' NOTES.txt already carry. The hand-rolled "cwaSecretRef IS UNSET" block in calibre-web-automated's NOTES.txt is gone: after the guard the render aborts first and that block is unreachable. minecraft-server's note stays true and now points at the guard. No "required" array in the schemas, and README guideline 12 now says why. The plan called for one; measuring it showed it could never fire: the key ships as null, so it is present at validation time, and JSON Schema's required tests presence, not null-ness. Making it fire means either dropping the null default or narrowing the type to "string", and both turn helm lint --strict red on the chart's own defaults. The schema therefore describes the key as required and required() enforces it. The README bullet on how null reaches the schema was also wrong in the case it was being applied to - a null chart default is not coalesced away - and now distinguishes the three cases. searxng: the claim "charts in this repo have no dependencies (README, guideline 13)" in the valkey template, in values.yaml and twice in _helpers.tpl has been false since #214 and cited the wrong guideline; dependencies are admissible and are guideline 14. The same sentence survives in other charts' helpers and needs its own round.	2026-09-22 20:03:27 +00:00
jklein	65cb33e5f2	calibre-web-automated: add a NOTES.txt worth reading twice (6.1.0+upv4.0.6) ... Prints what an operator would otherwise dig out of the templates: the rendered access URL or the concrete port-forward, the fields the 1Password item has to carry, and the traps of this chart in particular - the public default login, the ingest folder that deletes what it imports, the fixed 1Gi ingest claim, the one shared library claim, and why a change inside the 1Password item rolls nothing (subPath mounts included). Conditional on the values that actually decide something: ingress on/off, scaled to zero, an unset secret ref, and extra env entries. Part of #43.	2026-08-29 00:19:21 +02:00