#helm - December 2020

As @Erik Osterman (Cloud Posse) suggested, not sure if anyone has any experience with this ->https://sweetops.slack.com/archives/CQCDCLA1M/p1607475676220800

I'm trying to read an HTML file in and include it in a string as an annotation but having a difficult time due to what I assume is quotes/single quotes. Anyone done this before? Basically I'm including a static maintenance page as a ALB rule

We have a 3rd party helm chart that we are working with. it is an umbrella chart that has other umbrella charts. Probably like 3 levels of charts...many of the settings from the subcharts are not exposed in the root values.yaml. Was looking for a tool/script that will generate a values.yaml with all the values from subcharts

Is there a way to see the badly rendered values, so I can see where I made the mistake?

Error: YAML parse error on dgraph-lambda/templates/deployment.yaml: error converting YAML to JSON: yaml: line 34: did not find expected key
helm.go:81: [debug] error converting YAML to JSON: yaml: line 34: did not find expected key
YAML parse error on dgraph-lambda/templates/deployment.yaml
...

Doesn't help. I want to see how it was rendered so that I know how to fix it. Sometimes it's just a matter of indentation.

And it was... grrr... this is such a frustrating part of helm, makes it so painful to debug.

I'm not sure how to get this to work:

{{- if .Values.script.enabled -}}
apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ include "dgraph-lambda.fullname" . }}-config
  labels:
    {{- include "dgraph-lambda.labels" . | nindent 4 }}
data:
  script.js: {{ .Values.script.script }}
{{- end -}}

This get me:

[ERROR] templates/config.yaml: unable to parse YAML: error converting YAML to JSON: yaml: line 13: mapping values are not allowed in this context

The --debug flag should show you the bad yaml.