[
https://issues.apache.org/jira/browse/SLIDER-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981580#comment-14981580
]
Gour Saha commented on SLIDER-657:
----------------------------------
[~sherryxg] this is a wonderful idea. You are right, Ambari view prompts for
confirmation in its UI logic (providing its own force implementation). Hence
your new 002 patch does not break Ambari Slider View and any client integrating
with Slider API.
However this bug breaks backward compatibility for client users, which is
expected as per the nature of this fix. I am marking this fix version 0.90
where we will provide necessary release notes and update site documentation
with this client only backward incompatible change.
> Introduce --force switch for slider destroy command
> ---------------------------------------------------
>
> Key: SLIDER-657
> URL: https://issues.apache.org/jira/browse/SLIDER-657
> Project: Slider
> Issue Type: Bug
> Components: client
> Affects Versions: Slider 0.60
> Reporter: Gour Saha
> Assignee: Sherry Guo
> Fix For: Slider 0.90
>
> Attachments: SLIDER-657-001.patch, SLIDER-657-002.patch
>
>
> Slider destroy has irrecoverable implications where directories and
> registries are permanently deleted. For some applications this could mean
> loosing valuable data. It might be a good idea to introduce a {{--force}}
> switch, so that admins/application-owners are given a chance to ensure they
> know what they are doing.
> This is something in-line with *git clean*. When invoked by default it fails
> with a message saying {{-f}} is mandatory (unless the git config variable
> clean.requireForce is set to false). If the user is confident he/she will
> re-run the command with the force switch.
> Slider could do something similar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
