-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
RuntimeSDK: Improve Runtime Hook Swagger documentation #6505
Comments
/milestone v1.2 |
As the RuntimeSDK documentation has been merged now, it's probably time to revisit this issue. I'm not sure how much we want to document per hook in the Swagger schema, given the more extensive documentation we have in the book now (afaik we can only use plain strings for documentation in the schema). We also already did a few rounds of improving descriptions/godocs of the hook API types, which are also reflected in the Swagger schema. Is there anything else that we should do apart from re-reading the schema and see if makes sense as it is rendered in the Swagger-UI? @fabriziopandini Opinions? P.S. I think the current schema we have is already pretty good / maybe even better then what we have for our CRDs (especially considering that RuntimeSDK and the hooks are an experimental alpha feature) |
Let me make a pass on the current swagger doc in the beta releases, then I will come back |
Okay, thx. |
/close rif #6878 |
@fabriziopandini: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
User Story
As a user I would like to be able to get sufficient self-explanatory information to implement RuntimeHooks via the generated Swagger documentation/specification.
Detailed Description
This is a follow-up to #6455 (specifically: #6455 (comment) & #6455 (comment)). Goal of this issue is to extend the godoc comments of the request/response types and the description of the Hook (specified when registering the hook).
We should document things like:
Note:
/kind cleanup
/area runtime-sdk
The text was updated successfully, but these errors were encountered: