Bug 1378499

Summary:	[RFE] oc delete should come with user protection
Product:	OpenShift Container Platform	Reporter:	Eric Rich <erich>
Component:	RFE	Assignee:	Derek Carr <decarr>
Status:	CLOSED DEFERRED	QA Contact:	Johnny Liu <jialiu>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.4.0	CC:	aos-bugs, byount, ccoleman, deads, decarr, erich, ffranz, jokerman, mbarrett, mmccomas
Target Milestone:	---	Flags:	erich: needinfo? (decarr)
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-12 13:54:36 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 Eric Rich 2016-09-22 14:55:11 UTC

Description of problem:

When deleting objects oc delete should warn or prompt a user if they really want to delete the object. 

It should also give a warning that the operation is not recoverable.

Comment 1 Clayton Coleman 2016-09-22 16:35:28 UTC

This as been proposed upstream for explicit objects, but confirmation of default objects is not there.  Can you explain the use case under which someone calling delete is surprised that what they ask to be deleted is deleted?

Comment 2 Eric Rich 2016-09-22 18:30:40 UTC

(In reply to Clayton Coleman from comment #1)
> This as been proposed upstream for explicit objects, but confirmation of
> default objects is not there.  Can you explain the use case under which
> someone calling delete is surprised that what they ask to be deleted is
> deleted?

> oc delete all --all-namespaces

Is the command context where we have had customers be supersized that this deletes "everything".

Comment 5 Eric Rich 2018-03-12 13:54:36 UTC

This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.