trillian job createdb=false causes yaml parsing error

[crispysipper]

Description

since createdb is a one-off job, I don't want it to run after the initial installation of the sigstore stack. However when I set enabled=false for the createdb job as part of the trillian deployment, it produces an error like so when the app sync through ArgoCD:

error converting YAML to JSON: yaml: line 2: did not find expected key

this appears to be happening because the upstream template closes the outer if .Values.createdb.enabled too early, then renders nodeSelector, tolerations, and affinity conditionals outside the guard. When you set createdb.enabled: false but still define those keys, Helm renders dangling, indented fragments with no parent object.

As a workaround, I remove my values for nodeselectors/tolerations and the false flag parses successfully and the desired behavior occurs.

Version

0.7.24