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

Helm lint does not show error message #29

Open
davidshare opened this issue Dec 13, 2020 · 4 comments
Open

Helm lint does not show error message #29

davidshare opened this issue Dec 13, 2020 · 4 comments

Comments

@davidshare
Copy link

Thank you for creating this action.

I used the action to lint my helm chart before I attempted deployment, and the step fails each time but does not display what caused it to fail. Because of this, I don't know what I am dealing with since helm lint works on my local machine.

@WyriHaximus
Copy link
Owner

Hey @davidshare there shouldn't be any need for this action anymore. GitHub now includes helm3 environment, just haven't gotten around properly deprecating this action

@goshlanguage
Copy link

Unfortunate to hear that you're considering deprecating this action. For users who use things like act or the act operator to run against their environments, Github's supplied helm3 is unavailable by default, and this action is quite helpful.

@WyriHaximus
Copy link
Owner

Good to know @goshlanguage! As you might have noticed, haven't done a new release since I last commented here, so I haven't decided what to do. One thing I've been keeping in mind as an option, is to provide a Docker based back up in case helm3 isn't available, or when calling helm runs an unexpected version.

@WyriHaximus
Copy link
Owner

@goshlanguage An update on this: Currently building a home k8s cluster with raspberry pies and I'm finding out how much the default Runner environment provides and how much harder everything is when the runner doesn't have anything available. (Especially when all tooling assumes amd64.) So I've started to work on a way to always have Helm available using Docker.

@davidshare Are you still using this action and still running into that problem. In the upcoming v3 it switched to using nodejs. That will also solve #18 in a nicer way.

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

No branches or pull requests

3 participants