Comment 2 for bug 1833738

Rados GW is enabled by default at platform level as part of Ceph. Then stx-openstack only executes a chart that sets up rados-gw keystone enbpoints. The chart configures swift endpoint, it does not take resources afterwards.

This LP has two parts:
1. Make swift configurable at the platform level.
2. Apply rados-gw keystone configutation chart only if swift is enabled.

We made swift a default platform service as part of https://storyboard.openstack.org/#!/story/2004520 in commit https://opendev.org/starlingx/config/commit/754f49a3575b78517327c3a0a7556cc25de6a18b

The parts that enable swift by default will have to be reverted. Afterwards platform swift can be enabled by using "system storage-backend-modify ceph-store -s swift". Then the overrides to the chart can pick this up.

Question is: are we happy to have swift configurable through "system storage-backend-modify ceph-store -s swift"? Or do we want it through service parameter or a chart override?
I'm asking because the mechanism is already there, it needs to be enabled & retested (and probably parts of some other commits that made changes to this area of code reverted).