-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error converting YAML to JSON: yaml: line 22: did not find expected key #13044
Comments
@Marwen-TAALLAH please format your code by |
Done ! |
@Marwen-TAALLAH is there a step to process the master:
${ indent(2, redis_affinity) }
${ indent(2, redis_nodeSelector) }
${ indent(2, redis_default_tolerations) }
persistence:
enabled: false Specifically, the I'm not aware of helm supporting templating for the values file |
@banjoh The values.yaml file is causing a problem only when the redis chart is called as a module, when executinf the terraform apply locally, the file doesn't cause an issue !! |
Are you able to create a reproducer chart, say by creating a chart using |
@banjoh I am able to create the chart with helm directly without terraform, I am also able to create the chart with terraform, all of that with the exact same values.yaml I have provided. |
@Marwen-TAALLAH to rule out terraform as being the problem here, could you provide the I cannot run terraform, so I'm not able to ascertain whether this values file is valid as you say. Am looking to see the output of |
I am trying to create a redis helm chart via a module within a github workflow. The problem seems to be in the helm-values.yaml file in the module. It's an error converting YAML to JSON: yaml.
I have a workflow in github that executes a command that terraform apply a module that is in another github repo, in this module I have a helm-values.yaml that looks like this:
but I get this error:
I changed the manifest file to look like this:
But now i'm getting this error:
So i changed one more time to this:
But now I get this error:
The text was updated successfully, but these errors were encountered: