Bug 1462396 - oc rsh --timeout to be set ad default on per user basis
Summary: oc rsh --timeout to be set ad default on per user basis
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Derek Carr
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-17 04:04 UTC by Jaspreet Kaur
Modified: 2020-12-14 08:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-12 11:58:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaspreet Kaur 2017-06-17 04:04:22 UTC
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.

Yes

Comment 2 Kirsten Newcomer 2019-06-12 11:58:55 UTC
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.


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