-
Notifications
You must be signed in to change notification settings - Fork 32
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
Explicitly document all supported actions. #18
Comments
Unfortunately, it's not possible to document all the actions as this depends on the version of rancher you are running. The client is dynamic based off the schemas rancher presents and thus anything we document will never be accurate. |
Then why not provide a means for the user to discover them? At the very least, you could include the steps I took above. |
This is a generic, dynamic client that knows nothing about the API is talking to in advance other than that it follows our basic structure. Some of the things you can talk to it with have nothing even to do with Rancher or Kubernetes and are written by unrelated third parties. So putting in a list of the derived things it can do when pointed at one particular version of one product's API does not make a lot of sense. What you're proposing is very much like putting a list of websites cURL supports into their readme. The normal way people "discover" those is by looking at the API directly (via api-ui). If you wanted to put something in the readme that (only) told someone HOW THEY could generate the list for themselves for the API they are pointing it at, that would make some sense. |
The README.md file states the following:
If this is for Kubernetes in general, or other third party APIs as you state, then this should be documented. I don't see any documentation referencing "via api-ui" anywhere either. The current lack of documentation is insufficient as-is. Whatever can be done to improve this for users would be greatly appreciated. |
See also: rancher/rancher-docs#173 |
The README.md file references the API spec, but this is not sufficient for documentation.
This is the full list at the time of writing this:
gz#15364
The text was updated successfully, but these errors were encountered: