-
Notifications
You must be signed in to change notification settings - Fork 702
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
Add GetNamespaceNames, CreateNamespace and CheckNamespaceExists to resources plugin #3905
Conversation
Trying to find out which upgrade of |
02d0409
to
6501692
Compare
Excellent! Looking forward to having the |
resources plugin. Signed-off-by: Michael Nelson <minelson@vmware.com>
Signed-off-by: Michael Nelson <minelson@vmware.com>
c706682
to
ee2f1a3
Compare
Given this change is just the proto (and generated files), and you approved the subsequent one with the implementation, and didn't have any feedback other than the above for this, I'm going to assume that was a +1 :) |
Woops, sorry, you hadn't actually added a +1 to the next one either. I'll not land that until then. |
dashboard/tsconfig.json
Outdated
/* TODO(minelson): noImplicitReturns disabled until addressed in ts-proto: | ||
* https://github.com/stephenh/ts-proto/issues/432 | ||
"noImplicitReturns": true /* Enable error reporting for codepaths that do not explicitly return in a function. * /,*/ |
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.
Now that ts-proto
has fixed the issue, shouldn't we enable this back again?
I had just added a comment which I thought was published, but it was part of the PR review that wasn't sent 😄 |
Signed-off-by: Michael Nelson minelson@vmware.com
Description of the change
This PR adds the definition only to the resource.proto. Subsequent PRs will add the implementation for the Check and Create methods.
Benefits
Allows implementation of methods required for two call-sites in the dashboard that currently talk directly to the K8s API server.
Possible drawbacks
Applicable issues
Additional information