-
Notifications
You must be signed in to change notification settings - Fork 201
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
Can I explicitly ignore a field? #71
Comments
There is not at present, but I think this is a reasonable ask. I can envision a flag (that can be repeated) like |
No worries! I'll try and pull something together when I have a minute. Just wanted to make sure I wasn't missing something. |
👍 on this feature request! Would be useful for my use-case too! |
Would be good if this was implemented the same way as Bitnami's readme-generator-for-helm that you can specify fields to skip in the This would scale better when generating docs for multiple charts compared to using |
@K1Hyve @Pothulapati @mjpitz I needed something similar to this as well, but was able to implement it by generating the table myself in a custom template (I provide an example in an unrelated enhancement request I just raised here #107). |
PR for this: Add option for ignoring values #141 |
I'd prefer configuring which values to skip via a special doc comment directive rather than a flag for helm-docs cli. My reasoning / use case is setting some values on sub chart's values. Since those are (hopefully) documented in the referenced chart, it would be superflous to have documentation for those overrides generated in my chart. Alternatively the |
@Anticom doc directive is already merged. It's documented here: https://github.com/norwoodj/helm-docs#ignoring-values I don't know what are the plans for @norwoodj As the original question/feature request is resolved, I would close this issue. |
Oh, I've totally missed that. Thanks for the heads-up! 🚀 |
There are a few fields I don't want to show up in my README. Is there a way to explicitly ignore or exclude a field?
The text was updated successfully, but these errors were encountered: