I think the possibility of not having object-store in the cloud should be taken into account.
There is an existing option (set to True by default) which is related, however, its deprecated for removal to avoid having to manage an apache2 instance:
use_swift:
type: boolean
default: True
description: >
DEPRECATED FOR REMOVAL
Should the charm set up the product-streams endpoint with swift's URLs?
If this value is set to False, product-streams metadata will be hosted
on a local Apache server running on the unit and endpoints will be
registered referencing the local unit. This does not support HA
or TLS and is for testing purposes only.
I think the possibility of not having object-store in the cloud should be taken into account.
There is an existing option (set to True by default) which is related, however, its deprecated for removal to avoid having to manage an apache2 instance:
use_swift:
type: boolean
default: True
description: >
DEPRECATED FOR REMOVAL
Should the charm set up the product-streams endpoint with swift's URLs?
If this value is set to False, product-streams metadata will be hosted
on a local Apache server running on the unit and endpoints will be
registered referencing the local unit. This does not support HA
or TLS and is for testing purposes only.