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.
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
Update
tanzu
context APIs to support ClusterGroup #142Update
tanzu
context APIs to support ClusterGroup #142Changes from 2 commits
00c78b0
450decc
0d6933e
363c7ea
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 function only supports getting kubeconfig for the
tanzu
context-type and no other context type.Should we consider renaming this function to be more specific like
GetKubeconfigForTanzuContext
?Or
Should we consider supporting the
kubernetes
context-type and make this API more generic? cc @prkalle @vuil @marckhouzamThere 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.
Does renaming cause a backwards compatibility problem?
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.
Initially these methods were under
tae
package and it was not an issue as user has to call them astae.GetKubeconfigForContext
, but later due to renaming the context type totanzu
and re-organizing them underconfig
package, it is causing confusion. So, i feel it is good to rename to avoid confusion. I believe these changes are breaking ( I seeSetTanzuContextActiveResource()
signature also changed), so we can use this oppurtunity if possible (there should be only 2 affected pluginsproject
andspace
).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 feedback @prkalle and @marckhouzam.
I think all the APIs related to the
tanzu
context are experimental APIs and we should be able to make changes to the API at the moment. Also, my existing changes do update the API signature as well.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 will keep this thread open to get feedback from @vuil as well. However, I am not planning to do this rename as part of this PR. If we decide, I will create follow-up PR for the rename.
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 think the idea of supporting the kubernetes context-type is interesting.
I'm not sure if it would be easy.
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'd suggest keeping the name look into add suport the kubernetes context-type in a followup, since the usecase for wanting to use this API for tanzu context is not that different from when context type is kubernetes. I also think it should be quite straightfoward to add this support.