-
Notifications
You must be signed in to change notification settings - Fork 4
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
Migrate types and clients to a different location #4
Comments
I like the idea, we will benefit from having all CRDs, code generation scripts, Kubernetes clients, and the discussions surrounding the APIs on the same place 👍 Plus the modules imported on the other projects will be much easier handle. Lets make sure the initiative is registered for the next community meeting. |
For the record: following a meeting we have agreed that this is not a priority at this moment. As the projects grow we may adopt this but at this stage it is not necessary. |
Wouldn't it be good to have the kubernetes types and clients into something like a "shipwright-io/apis" ? If we plan to migrate kubectl-image kubectl plugin to shp client that could be a good idea.
Is there already a centralized place for the shipwright api types/clients ?
The text was updated successfully, but these errors were encountered: