This patchset updates all the requirements for charms.openstack,
charm-helpers, charms.ceph, zaza and zaza-openstack-tests back
to master branch.
Change-Id: I0f5b28437fda22b09fb0d9346fa5581f6a995f72
* charm-helpers sync for classic charms
* build.lock file for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure stable/21.04 branch for charms.openstack
- ensure stable/21.04 branch for charm-helpers
Change-Id: I8b159e2fd0eadecb23c580804ec9b3609b14fdb1
Update tox.ini to lint unit_tests, clean lint.
Add src/README.md placeholder to prevent inheritence of the
lower layer readme file in the built charm.
Add src/tox.ini and test-requirements for Amulet prep.
Update metadata.yaml for series.
Update tox.ini to minimize and clarify pep8 ignores.
Resolve flake8/pbr test-requirements version range conflict.
Mock apt in unit tests.
Add required tags data in src/metadata.yaml for charm proof.
Use openstack/charms.openstack proper in test-requirements
instead of a user space fork.
Update src/layer.yaml repo value to point to official location
and remove unnecessary options.
Change-Id: I5ca9e6cf9f8f91b3ce0ec3b48cf63535ca37c0f7
Working charm with unit tests. Various features:
Change the install ownership for token store
It turns out that the 'user' that creates the token store, is the only one that
can access it, apart from root. As Barbican uses a 'barbican' user for the
barbican-worker process, we need to create the token store with 1777 perms (see
https://github.com/opendnssec/SoftHSMv2/issues/185) and also create the initial
token using the barbican user.
Add an initial README.md: This describes the charm, where to get help
and how to use it.
This is a barebones charm (as part of this commit) which only connects to the
prinical barbican charm and announces its name (as softhsm). Next steps are to
install and configure the software for the softhsm and determine what should go
across the charm relation.
Alex Kavanagh