Fix bug which deleted project bucket instead of project contents only #1172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
A user at NGI Stockholm noted that he created a project, uploaded data, used
dds data rm --rm-all
and then tried to upload data to the same project. The last step resulted in a long traceback complaining that there was no such bucket. Turns out thedelete_project_contents
used by theRemoveContents
endpoint, and by the project-deleting/archiving also removes the buckets which is not intended.In this PR I have changed the name of the S3Connector method to
remove_bucket_contents
instead ofremove_bucket
and added a kwarg calleddelete_bucket
(default False). When the projects are being archived or deleted, this should be set to True.Fixes DDS-1283
Type of change
Checklist:
Please delete options that are not relevant.
Formatting and documentation
Tests