Bug 1462396 - oc rsh --timeout to be set ad default on per user basis
oc rsh --timeout to be set ad default on per user basis
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Derek Carr
Xiaoli Tian
Depends On:
  Show dependency treegraph
Reported: 2017-06-17 00:04 EDT by Jaspreet Kaur
Modified: 2018-02-08 08:36 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jaspreet Kaur 2017-06-17 00:04:22 EDT
3. What is the nature and description of the request?

oc rsh --timeout to be set ad default on per user basis

4. Why does the customer need this? (List the business requirements here)

Our developers are asking for is a mechanism to set a default for their 'oc rsh' command, so they don't have to set a manual --timeout option every time they use the command.

5. How would the customer like to achieve this? (List the functional requirements here)
It could be set by having an option that could be set in one of the files in ~/.kube/ and then, if it wasn't specified there, then it could default to 10 seconds. So each developer could specify their own default timeout, but still be able to override that using the --timeout option when needed. 

6. For each functional requirement listed in question 5, specify how Red Hat

and the customer can test to confirm the requirement is successfully implemented.


Note You need to log in before you can comment on or make changes to this bug.