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.
The tvault-contego.conf and tvault-object-store.conf files have jinja
templating to remove whitespace before and after the endif control
segments, which lead to invalid ini style config files. Correct the
white space removal directives.
* 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
Add update-trilio action which can be run after a Trilio
upgrade.
Trilio sometimes updates packages in package repositiories that
require DB migrations or config file changes. Since these package
updates are not applied by the charm as they would be by changing the
openstack-origin or triliovault-pkg-source the charm has no event to
react to to automatically perform the post package upgrade actions.
This change adds an action `update-trilio` which can
be run to apply the changes.
Remove the experimental status from the S3 options. Update the
README documentation to provide information on configuring the
appropriate backend to use for NFS or S3 storage.
This change is mainly copied from the corresponding change to
trilio-wlm ( I7836754529a8b5d067a86077e1e004fa2f53ec6e ). Bug
1933809 *1 is tracking the consolidation of duplicate code.
