* 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 requirements.txt to pin charm-tools to 2.8.3
* Update tox.ini to change the build parameters.
* This upgrades from <2.7 which adds reproducible charms
* Bug was fixed that controlled the default output directory
doesn't get 'builds' appended. The tox change puts it
back so that stable & master both build to the same
directory. This may be reviewed in the future.
Change-Id: If175d58b7b663927d7e7be1c44550a9b8aaa5d79
* charm-helpers sync for classic charms
* charms.ceph sync for ceph charms
* rebuild for reactive charms
* sync tox.ini files as needed
* sync requirements.txt files to sync to standard
Change-Id: I59137f0bc2a0c5ee15f52bd03afefa275e9a011b
The bundle disco-stein was in the dev bundles because
a bug with the Python 3.7 syntax prevented the success of
the deployment of HA clusters. This bug is fixed, we can
reintegrate disco-stein in the gate bundles.
Other small additions:
- removing sitepackages in tox.ini to avoid test env pollution
- skip_missing_interpreters in tox.ini set to False to avoid false
positives by skipping missing interpreters.
LP Related-Bug: #1823718
Change-Id: I432a562efb84e486034f97f433186a31a80d4b2d
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Note that python35-charm-jobs is retained since this charm is supported
on Xenial.
Change-Id: I8a8bbce4e79a7959f1735902c87d9d1ab02b9957
Story: #2005924
Task: #34228
This technique was borrowed from the tox "cover" environment in
openstack/nova's tox.ini. This leverages the fact that stestr lets
you override the python executable via the PYTHON environment
variable. Doing this allows us to easily generate coverage for our
unit tests.
An important caveat is that this does not provide any coverage for
tests via zaza, amulet, etc. It is purely focused on the unit tests.
Note that this replaces the previous .coveragerc; coverage
configuration is instead pulled from tox.ini.
Change-Id: I6c57c238e19a3e7e500f81135075cdcb11ac3127
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: Icbaef58649b5b21d932a7f497a61faa322bad03b
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Reactive source charms are Python3-only, but have py27 unit tests
declared in project-config.
The Tox tool recently changed behavior. It used to pass when a tox
target was missing commands. Now it fails in that case.
This commit places a py27 no-op shim to allow gate tests to pass,
effectively restoring the original behavior for these py3x-only repos.
Change-Id: Id421159a7fe5ab330a302172790994079e96319b
Partial-Bug: 1642981
All OpenStack Charms now contain identical tox.ini files,
not to be modified or made unique within each charm repo.
This is to ensure consistency across charm repos in tox
target naming, approach and purpose, also giving the
charm dev and test experience additional consistency.
Change-Id: Ie84a6fa14bf68b49376cd9ec560afbe8e29b578d
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.