overwrite configuration should be replaced with an action based approach to disk management

[Chris MacNaughton]

It is currently possible to delete data in the swift-storage charm via configuration and this should not be an option. We should follow the ceph-osd approach of having a zap-disk action

[Chris MacNaughton (chris.macnaughton)]

This bug is replacing https://bugs.launchpad.net/charm-swift-storage/+bug/1796651 as the linked one follows a dangerous precedent

[Chris MacNaughton (chris.macnaughton)]

I'm working on a fix for this at https://review.openstack.org/#/c/643593/

[Alex Kavanagh (ajkavanagh)]

Changing to won't fix; there is a review (that is going to be abandoned) which can be resurrected if there is still an appetite for this feature addition. Note that the world has changed slightly, and that the basic_deployment.py tests in the patch would need to be migrated to a zaza-openstack-tests patch. Patch also needs rebasing.

[OpenStack Infra (hudson-openstack)]

Change abandoned by "Alex Kavanagh <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/charm-swift-storage/+/643593
Reason: It's a feature addition, but hasn't been landed in 4 years. This may be resurrected if there is still a demand for this feature.