mirror of
https://github.com/shankar0123/certctl.git
synced 2026-06-07 13:41:30 +00:00
shankar0123
c70bb071f9
Commit9155ec9introduced a YAML `#` comment block above the tlsConfig branch that referenced `{{ if ... }}` and `{{ fail }}` as literal text. Helm's template engine scans for `{{ ... }}` action delimiters everywhere in the source — it does NOT respect YAML `#` comments. So Helm parsed the multi-line sequence {{ if .Values.monitoring. # serviceMonitor.tlsConfig }} as a single template action containing an invalid `#` token, which aborted the WHOLE chart render with: Error: parse error at (certctl/templates/servicemonitor.yaml:51): unexpected <.> in operand That's why all five B3-helm-chart-coherence render modes (default, external-Postgres, production-hardening, sessionAffinity, viaHook) failed simultaneously onf7fcd1e— the parse error fires before any mode-specific values get applied. Fix: replace the YAML `#` block with a Helm `{{- /* ... */ -}}` comment block. Helm strips the comment body before template execution, so descriptive references to `{{ if ... }}` / `{{ fail }}` inside the comment are safe. Also rewrote the `{{ fail }}` message string to drop the inline backtick-quoted `{ insecureSkipVerify: true }` shape (literal `{` could have re-tripped the same scanner) in favor of `insecureSkipVerify=true`. Lesson: descriptive references to Helm template actions inside chart templates MUST live in Helm-comment blocks, never in YAML comments. The G-3-env-docs-drift fix inf7fcd1eis unaffected — this is purely the B3-helm-chart-coherence regression introduced by9155ec9.