-
Notifications
You must be signed in to change notification settings - Fork 175
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
feature request: "Strict mode" #169
Comments
I think this could go pretty well when we are adding documentation to multiple helm charts. Currently, the only that it's done is just by seeing if the value is empty on the generated table. For multiple charts it does indeed make sense. In the future it may even go well with subchart checking that is discussed in the following issues:
Are you still willing to add a PR? @edmondop |
@Nepo26 no I wanted to check if there was interest, but I am happy to take care of it soon! |
I think there is interest for sure. We are revamping the repo, so I'll not be able to contribute to this issue yet. So feel free to work on it whenever you are able. |
Hey @edmondop I'll look into your PR today. Sorry for the delay. |
@Nepo26 any release on the horizon for 1.11.1? |
Yes, Sorry for the late response. By the end of next week the latest merges will be published. Just need to finish cleaning up documentation. |
Hey @edmondop. Already published the release. If you can, check it and respond if everything is OK.
|
Is this close to being completed? |
Hey @jhoover4, this function has already been released. |
Oh wow, how do I use it then? I tried Is it the |
Yes. It's the |
Hey @Nepo26 its really easy to see. You can run it against the example charts, like so:
That exit value needs to be 1 since it failed. To use with a CI we need the proper exit value. |
Hmm, that is correct. It reports the correct missing values but not returns the correct exit value, right? |
It also seems like it is not returning all missing values. Actually, I just tested here locally and it returns for all charts. |
The exit value seems to be a problem outside the change @jhoover4 . I went back and look to the change, and as you see here:
the error is correctly returned upstream, but it doesn't seem the code above is handling the error and returning a -1. The problem is in |
Yes that makes sense. Is there still a bug in validating or is the bug only in handling errors returned by the validating function @jhoover4 ? |
I think there's a bug in both like you noticed @edmondop 😅. It spits out warnings when those should be errors (from what I'm getting from the docs) |
Is strict linting supposed to work with the new-style comments or just the old-style one? This fails: # -- Number of replicas
replicaCount: 1
But this works: # replicaCount -- Number of replicas
replicaCount: 1
|
Also, the Docker container doesn't seem to like the outputted error message:
|
This novel feature is genuinely splendid! Despite minor issues with the exit code and the incorrect evaluation of the abbreviated format, I wholeheartedly appreciate it! Concerning the behavior (whether to terminate with an error or not, etc.), in my modest opinion, the optimal approach, particularly in terms of backward compatibility, would be to conclude with an error only if, for instance, an additional option is employed... Perhaps |
Hey guys just wanted to check in. Do we still need any help to get this done? |
As it's been radio silence for a while, I guess the answer is yes? 🤔 |
Same problem here, would be nice to have a non-zero exit code when there are errors running on strict mode. I'm trying to workaround that on pre-commit hooks using this configuration: - repo: local
hooks:
- id: helm-docs-strict
name: Helm Docs Strict
language: system
entry: /bin/sh
args: [-c, "helm-docs --documentation-strict-mode 2>&1 | grep \"Error parsing information\"; exit $(($? == 0 ? 1 : 0))"]
always_run: true
pass_filenames: false
require_serial: true |
Enforcing documentation guidelines via CI/CD check is desirable in some context, and the same way a linter could complain about a non documented function, it would be great if helm-docs could complain about a non documented value.
I am happy to take care of this if there is a green light and prepare a pr
The text was updated successfully, but these errors were encountered: