-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Mix task for generating CRD swagger #26
Comments
In my current testing the process is a little bumpy as it will require two compile passes. One to compile the CRDs so that mix can pick them up and a second to compile the client with the swagger file that mix generates. |
I have a suggestion (not sure this is related): how about we stick to simple code generation instead of metaprogramming + compilation? This was one of the most irritating things about |
No longer necessary, underlying k8s library does API discovery. Will need to just push the CRD and everything should work fine. |
In working on the k8s client I’ve alotted for extending the client with a custom swagger spec.
To auto generate the routes in the client we would need a task that takes a k8s version, downloads the swagger spec, then merged in the swagger operations and definitions for each CRD.
This will allow for simple CRUD style interactions with CRDs in the k8s API.
resources = K8s.list(“mygroup/myversion”, “MyCRDType”)
The text was updated successfully, but these errors were encountered: