Using KeyPrefix does not delete the s3 bucket after "sls remove" command.

This is a:

• [] Feature request or change
• Bug report

---

For bug reports:

Expected behavior

“sls remove” should remove the bucket

Actual behavior

objects was deleted but the bucket remains, although it is empty but in a long run it will pile up on my aws account.

Steps to reproduce

Added KeyPrefix to yml file.

custom:
   client:
     keyPrefix: 'samplepref'

Below is the result of “remove” command.

I think this block of code has something to do with the behavior.

• **Operating system:osx
• **serverless-finch version:2.8.0
• serverless.yml that produces bug:
• Command that produces bug:
• Other details:

---

For feature requests or changes:

Current behavior (if any)

Proposed behavior

Proposed implementation deatils (optional)

Justification

[fernando-mc]

@mikejpeters - I also prefer clean sensible defaults so as long as we release this with a major version bump I’m fine with it. I agree it probably makes sense and there’s aren’t many people who would object to it but it does change default behavior destructively and there’s always some weird use cases we can’t predict.

When including this:

1. Add a warning to release notes
2. Bump a major version

Then we’re covering our bases and should be fine.

[mikejpeters]

Thanks for the response. I’m assuming you wouldn’t want this plugin to delete the bucket if there are still other objects i (e.g. in your case feature branches)?

@fernando-mc can you weigh in on this again when you have a chance? If the plugin deletes the objects at the prefix, and then only deletes the bucket if it’s completely empty I don’t see a downside. But maybe I’m missing some danger / use case? Having a new option like “force remove bucket” is safer but IMO less user-friendly. I like having smart defaults / less options, even if it means releasing a new major version with breaking changes