-
Notifications
You must be signed in to change notification settings - Fork 879
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
Allows the release namespace to be overridden #909
Conversation
Hi @KhizerJaan, thanks for your interest and PR! Please could you provide some more context about why this is useful? |
Hello @tomhjp , If Vault Helm Chart is being used as dependency in another helm (umbrella) chart, it is deployed to umbrella chart release namespace . This PR would enabled to override namespace for Vault Helm Chart. |
@tomhjp kindly review and merge the pull request at your convenience. I have umbrella chart use case and am blocked by it . default namespace is set to |
Thanks for the explanation, that makes sense. This seems like a nice improvement to merge then with a few additions. Please could we add some bats unit tests for each resource, a default empty value in the Values file, an entry in the schema, and a short changelog entry under unreleased improvements? Happy to help out with any of those, just let me know if you need some pointers or assistance. |
Sure. Highly appreciate the feedback and suggestions @tomhjp . I will incorporate the suggested changes, and submit a revised version that addresses the feedback provided. |
@tomhjp I have incorporated the suggestions provided. |
@tomhjp Could you please consider merging this PR? Alternatively, I would greatly appreciate any feedback you might have. |
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.
Thanks for the changes so far - just a few more small suggestions and then I think this is ready to merge.
I ran the CI and a few unit test failures came up FYI. Judging from the test names, looks like they should be trivial fixes.
|
@tomhjp Thank you for suggestions . highly appreciate it . I've updated regards to your suggestions . PTAL |
@tomhjp PTAL |
@tomhjp can this be merged please. |
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.
Sorry, the changelog changed in main since my last review - please could you rebase/merge in main to make sure the changes stay in the unreleased section when this is merged? Otherwise LGTM
Co-authored-by: Tom Proctor <[email protected]>
@tomhjp branch synced . PTAL |
@tomhjp can you please merge this PR? I've synced with main . or it would be great if you have any feedback. |
I've just run the tests again to prepare for merging, but it looks like the same ones from before are still failing. Do you need some help getting going with running them locally?
|
@tomhjp previously results were escaped like this |
Looks like that's done the trick, thanks. The other way to fix it would be to add |
Problem:
Root Cause:
{{ .Release.Namespace }}
Solution: