Add suppot for Trilio encryption options TRILIO_ENCRYPTION_SUPPORT
and OPENSTACK_ENCRYPTION_SUPPORT. TRILIO_ENCRYPTION_SUPPORT should
set to True for trilio > 4.2. OPENSTACK_ENCRYPTION_SUPPORT should
be set to True if Barbican is present in the deployment. It would
be nice if Barbicans presence was detected via a relation but since
this option is going in Trilio 5.X exposing this as a charm
option is a tactical fix. As part of the work the charm classes
were restructured a little as this charm does not support 4.0.
Due to a build problem with the reactive plugin, this change falls back
on overriding the steps and doing a manual build, but it also ensures
the CI system builds the charm using charmcraft. Changes:
- add a build-requirements.txt
- modify charmcraft.yaml
- modify osci.yaml
-> indicate build with charmcraft
- modify tox.ini
-> tox -e build does charmcraft build/rename
-> tox -e build-reactive does the reactive build
- modify bundles to use the <charm>.charm artifact in tests.
and fix deprecation warning re: prefix
- tox inception to enable tox -e func-test in the CI
- Pin everything in wheelhouse.txt for bionic and focal support.
This will need updating when the charm channels are created.
* charm-helpers sync for classic charms
* sync from release-tools
* switch to release-specific zosci functional tests
* run focal-ussuri as smoke tests
* remove trusty, xenial, and groovy metadata/tests
* drop py35 and add py39
The need to sync in the tox/pip changes for setuptools < 58 that is used
in other charms. Reactive charms depend on charm-tools, which depends on
blessings<=1.6 which uses 2to3 that is deprecated and removed in
setuptools 58.0.
