make destroy-all: s3 and fs fixture buckets should use force_destroy: true

[brainstorm]

Software version (git hash, date, branch)

093a538 (HEAD -> master, origin/master, origin/HEAD) HEAD@{0}: pull: Fast-forward

Expected behavior

make destroy-all should complete cleanly, automatically and without interactive distraction(s) for the developer.

Actual behavior

Terraform rightly complains that the buckets are not empty and halts the destruction of the resources/data. The fixture data should be eliminated without question as it can be replaced easily and has little "unique" value.

Steps to reproduce the behavior

make destroy-all

Wrapping up

As you can tell by the action (destroy-all), I'm giving up on HCA until it reaches higher levels of maturity deployment-wise and as a community (Slack only being used for announcing physical standups instead of actually answering questions from external third parties, referring to (internal?) private repos such as dcp-infra, client side tools still not up to speed, etc...).

It was fun to get to know its architecture, but as of today there are too many deployment hiccups and unknowns to further recommend this project to third parties... yet and IMHO.

So Long, and Thanks for All the Fish! Specially Trent, Kozbo and Brian, your feedback was really appreciated ;)

[kozbo]

Thanks for all of your contributions @brainstorm! Sorry to see you go. Would it be possible to set up a call to be sure that we have all of your concerns captured? It is true that we are focusing on getting our first deployment hardened right now, but it is our goal to make deployment and reuse straight forward. I would like to talk to you about your requirements. Please reach out to me on slack if you have the time for a call next week.

[Bento007]

It's by design that it's not easy to destroy DSS buckets.