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
Allow namespace to be set by programs consuming helm. #6798
Conversation
Signed-off-by: Aaron Mell <amell@lumindigital.com>
Would you mind writing a unit test to cover this? |
@bacongobbler Sure, were you thinking a test to verify that the namespace is correct? or something else? |
Labeled as breaking because it is changing a publicly exported function signature |
bc2cd3c Signed-off-by: Aaron Mell <amell@lumindigital.com>
@bacongobbler @thomastaylor312 I reworked my change to reduce the scope, I think its a better way to fix it than changing the Namespace scope. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does look much cleaner. Just one thing to remove
Signed-off-by: Aaron Mell <amell@lumindigital.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll let @bacongobbler give this one more look because he started review
Signed-off-by: Aaron Mell amell@lumindigital.com
When consuming the helm client, there is no way to correctly set the namespace except via an env variable, and that doesn't work with terraform possibly running the client concurrently in multiple namespaces.
I'm not sure if you want to expose Namespace. If thats the case, maybe a SetNamespace function?