-
-
Notifications
You must be signed in to change notification settings - Fork 295
include-needs
also includes transitive release-dependencies
#1003
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
Labels
bug
Something isn't working
Comments
@pathob PR is welcome. |
I will not be able to fix this. I found it when trying to add the |
@pathob I will fix this. Thanks so much. |
@pathob got it. I prepare the v1 version recently. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Operating system
Docker
Helmfile Version
0.156.0
Helm Version
3.9.0
Bug description
As stated in the Helmfile CLI documentation,
--include-needs
should only include direct dependencies whereas--include-transitive-needs
would include direct and transitive dependencies.I'm a super newbie to Go and in my projects we are currently only using
--include-transitive-needs
, but I've already wondered how--include-needs
is supposed to work after looking at the code here, here, here, here and here. I guess--include-needs
is broken since this change last year.Look at these jobs for this helmfile.yaml where only releases 2 and 3 should be templated / linted:
I guess apply, diff, sync etc. are affected too.
Example helmfile.yaml
Error message you've seen (if any)
None
Steps to reproduce
helmfile <template|lint|?> -l name=release3 --include-needs
Working Helmfile Version
0.147.0 (probably)
Relevant discussion
No response
The text was updated successfully, but these errors were encountered: