Skip to content
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

postfix secrets.yaml include path doesn't include any parent-chart path #121

Closed
stela opened this issue Jun 20, 2017 · 3 comments
Closed

Comments

@stela
Copy link

stela commented Jun 20, 2017

When attempting to use postfix as a subchart, its deployment.yaml appears to refer to the wrong path of the postfix secrets.yaml:

[debug] CHART PATH: /Users/.../myapp

Error: render error in "myapp/charts/postfix/templates/deployment.yaml": template: myapp/charts/postfix/templates/deployment.yaml:14:28: executing "myapp/charts/postfix/templates/deployment.yaml" at <include (print $.Cha...>: error calling include: template: no template "postfix/templates/secrets.yaml" associated with template "gotpl"

I guess the problem is that in postfix's deploy.yaml:

     annotations:
        checksum/secret: {{ include (print $.Chart.Name "/templates/secrets.yaml") . | sha256sum }}

this evaluates to postfix/templates/secrets.yaml instead of myapp/charts/postfix/templates/secrets.yaml? However I tried unpacking the postfix .tgz archive and patching its contents instead of referring to it from requirements.yaml, but didn't get that working yet either.

@goruha
Copy link
Member

goruha commented Jun 20, 2017

@stela Absolutely right.
That is problem of old helms.
In new versions they suggest different way to calculate sha256 code for secrets and configmaps.
I will update chart asap.

What version of helm do you use?

@goruha goruha self-assigned this Jun 20, 2017
@stela
Copy link
Author

stela commented Jun 20, 2017

Thanks @goruha!
I'm using the latest helm from homebrew at the moment (2.4.2 it seems, however see helm 2.5 was just released so will probably want to upgrade when it's in homebrew) together with minikube.

@osterman
Copy link
Member

This should be fixed now. Let us know if it's not working for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

3 participants