-
Notifications
You must be signed in to change notification settings - Fork 263
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
Move shared code to knative/client-pkg #1591
Comments
This issue is stale because it has been open for 90 days with no |
/remove-lifecycle stale |
This issue is stale because it has been open for 90 days with no |
/remove-lifecycle stale |
We discussed this with @dsimansk on today's WG meeting. There are some areas which are even broader in scope than client, and are related to command line apps in general, like:
Maybe others as well. All of this are command line related, and there are other command line tools that we have apart from client and plugins: test-infra tools, hack tools. Just in last week, I've added 3 command line tools: knative/test-infra#3513, knative/test-infra#2995, knative/hack#222. So, I think we could benefit from knative's commandline package. At the same time, adding those to client-pkg isn't helping as client has deps which simple command line tools don't need. I had an idea to fix this. We could use Go 1.18 workspaces, and hack's support for it knative/hack#205 to create commandline package in go 1.18
use (
.
client
commandline
) |
Since we have now
knative/client-pkg
for holding shared client code that can be used bykn
but also plugins, we should move the client API to this repository (and while doing so, thinking about cleaning it up)The text was updated successfully, but these errors were encountered: