Red Hat Bugzilla – Bug 1012497
swift: swift delete <container> should have a warning like rm unless used with --force
Last modified: 2016-04-26 11:39:59 EDT
Description of problem: currently if you run swift delete <container> than the container and all files will be deleted. I think that much like the rm command we should add a --force or rf so that either a warning appears or user knows what they are doing and adds the --force. Version-Release number of selected component (if applicable): openstack-swift-1.8.0-6.el6ost.noarch How reproducible: 100% Steps to Reproduce: 1. create a container with several files 2. run: swift delete <container> 3. Actual results: container and all files will be removed without a warning Expected results: we should not remove a whole container with no warning or a --force added (much like rm command) Additional info:
https://bugs.launchpad.net/swift/+bug/1231495
Isn't it a matter of personal preference? We have this awful redhattism of aliases for rm/cp/mv for root, which I always delete from /root/.bashrc. I suppose it sets a precedent, but if we do the same for swift(1), then we draw the same downsides -- only worse because there's no separate mode for scripting in Swift client. You don't want everyone to have separate scripts for RHOS, do you?
as you said, this is a personal preferences but RH releases do go out with aliases for rm and so on and I don't think that all people delete these preferences. in facet, I worked in support for production servers where we added additional protection for some things since someone running with root or sudo user might accidentally delete financial information for the entire east cost :). If you think this is problematic however, this can always be a configurable value no?
Warnings are client side anyway, so moving to client.
here is the upstream bug: https://bugs.launchpad.net/swift/+bug/1231495 please look at comment: https://bugs.launchpad.net/swift/+bug/1231495/comments/1
This is an upstream RFE, not a RHOS bug. It's properly filed upstream by the reporter so I see no reason to track this for RHOS.