swift delete should have a --force for delete of all container
Bug #1231495 reported by
Dafna Ron
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Object Storage (swift) |
Opinion
|
Undecided
|
Unassigned | ||
Bug Description
I think that swift delete <container> should not delete the container unless used with --force (or --rf) or that we should have a warning that all files under the container will be deleted much like rm command would work
way to reproduce:
as user admin create a container and upload several files
run: swift delete <container>
container and all files are deleted with no warning
| Changed in swift: | |
| status: | New → Opinion |
Revision history for this message
| clayg (clay-gerrard) wrote | #1 |
To post a comment you must log in.
I think we'd have to do a major version bump for the client or a deprecation warning?
If people already have shell scripts using this syntax we'd break them by requiring a --delete.
Maybe we could get away with it if we detected interactive terminal? Another route might be to add an environment variable that will require confirmation, or a safe-delete command that people could shell alias?
I don't think this is a bug, it's certainly operating as intended - but maybe the intention is undesirable?
This isn't the first time this has come up:
https:/