[Add] Allow specifying helm secret namespace for cluster scope objects #323
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, the helm secret namespace is taken from the namespace of the object which is being passed to `ActionClientFor`. When the action client is created for cluster scoped objects, the namespace has to explicitly set in their metadata. This PR introduces an option to specify the namespace through the context instead.
|
Realised that there is a ObjectToStringMapper to solve this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the helm secret namespace is taken from the namespace of the object which is being passed to
ActionClientFor. When the action client is created for cluster scoped objects, the namespace has to explicitly set in their metadata. This PR introduces an option to specify the namespace through the context instead.