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

Cannot use absolute chart path #743

Closed
BenBlaisdell opened this issue Jul 5, 2019 · 7 comments · Fixed by #753
Closed

Cannot use absolute chart path #743

BenBlaisdell opened this issue Jul 5, 2019 · 7 comments · Fixed by #753
Labels

Comments

@BenBlaisdell
Copy link

When I use an absolute chart path (starting with /) helmfile drops the starting slash and treats it as a relative path

Building dependency Users/my-user/charts/my-chart
in /Users/my-user/my-helmfiles/helmfile.yaml: in .helmfiles[1]: in releases/env/helmfile.yaml: helm exited with status 1:
  Error: could not find Users/my-user/charts/my-chart: stat Users/my-user/charts/my-chart: no such file or directory
@bitsofinfo
Copy link
Contributor

agree would be great if we could reference non-relative resources

@BenBlaisdell
Copy link
Author

I probably should have mentioned that this is a regression in my initial post. My org did use absolute paths (referencing charts in a local directory passed by environment variable). I noticed that this no longer works after upgrading to a newer helmfile version (although I'm not sure which version caused the regression).

@mumoshu mumoshu added the bug label Jul 10, 2019
@mumoshu
Copy link
Collaborator

mumoshu commented Jul 10, 2019

Thanks for reporting! I'll take a look and add a regression test for it as well.

@osterman
Copy link
Contributor

@mumoshu I think we're having this problem as well. @maximmi will confirm.

mumoshu added a commit that referenced this issue Jul 12, 2019
mumoshu added a commit that referenced this issue Jul 12, 2019
@mumoshu
Copy link
Collaborator

mumoshu commented Jul 12, 2019

#753 should fix this and it's included since v0.80.1. Would you mind trying, and report back if the problem still persist?

@BenBlaisdell
Copy link
Author

Problem's fixed; thanks for the quick response!

@mumoshu
Copy link
Collaborator

mumoshu commented Jul 12, 2019

Wow! Thanks a lot for your quick confirmation 😄

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

Successfully merging a pull request may close this issue.

4 participants