Diagnose scope, whitespace and YAML failures

Understand the likely causes

• Context changes can hide Release from dot, whitespace trimming can erase required newlines and direct helper insertion can ignore destination indentation. A wrong input shape can mimic a scope problem, so preserve both the failing source and typed input.

Classify the earliest error

Start with the earliest diagnostic rather than the most familiar symptom. A template evaluation error means text production stopped before a usable document existed. A YAML parser error means text was produced but its structure could not be read. A receiving API schema error is later still. Do not respond to all three by changing indentation. Reduce the chart to the smallest synthetic failing block while retaining required context and metadata; remove private values without changing their types or nesting.

Draw the context map

Write the value of dot at the template entry, inside each with and inside each range. Identify whether a helper receives the full root or a custom dictionary. Root $ refers to the context supplied to that template invocation, so a helper cannot assume it always sees the original chart root. Capture a required release name before entering a block or pass it explicitly. Do not add a fake Release subtree to user values to compensate for a context mistake.

template entry: dot = chart context
inside with .Values.settings: dot = settings map
inside range .Values.channels: dot = current channel
helper called with dict: dot and root = supplied dictionary

Inspect output line boundaries

For a YAML failure, inspect the generated text around the reported line and neighboring keys. The parser line may identify where it noticed a problem rather than where the template introduced it. Check trimming on both sides of conditionals, whether a parent key remains with no children and whether nindent uses the actual destination depth. The first serialized line deserves special attention. Keep present and absent cases side by side; a populated optional block can accidentally supply the newline that masks the absent-case bug.

Repair and preserve a regression case

Use include when helper text needs a formatting pipeline, pass the intended context explicitly and preserve required newlines. Keep string quoting tied to the receiving field type rather than adding quote everywhere. After the minimal fix, inspect default, empty and populated cases and assert the intended subtree. This guide executes no Helm renderer or YAML engine and fabricates no error transcript. It provides a diagnosis sequence whose environment-dependent checks must be performed separately with an approved local client and synthetic inputs.

Keep it from recurring

• Keep helpers small, namespace their names, document caller context and retain empty-input fixtures. Review rendered output during changes to whitespace markers; template source indentation alone is not a sufficient visual check.