| Summary: | oc get documentation | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Dan Yocum <dyocum> |
| Component: | oc | Assignee: | Maciej Szulik <maszulik> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Xingxing Xia <xxia> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 3.3.0 | CC: | aos-bugs, deads, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-21 09:08:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Dan Yocum
2016-09-14 16:37:02 UTC
> oc get help does not contain documentation to list the available templates. For example, this exists, but is not documented:
Right now, the list of available resources that is printed on `oc get` is hardcoded upstream. Ideally, we would want to "discover" available resources through the server in a future update.
Related upstream PR [1] and proposal [2]. 1. https://github.com/kubernetes/kubernetes/pull/51324 2. https://github.com/kubernetes/community/pull/1017 @David, I'd be in favor of using discovery to generate a list of resources that you can run against `oc explain`, if no other arguments are passed to the `oc explain` command. That's fine. Open it upstream. This is addressed in current release. |