Browse Source

Distribute direct charm dependencies

Do not rely on system installed Python packages but distribute the
direct charm dependencies as part of the charms wheelhouse.

As the span of distributions we need to support with reactive
charms widens we will run into compability problems with the
current model.

For further reference see juju/charm-helpers#341 and
juju-solutions/layer-basic#135

Change-Id: I11fb4020dc358c40bf9c1870e94186ba7e97c2db
changes/73/676673/4
Frode Nordahl 3 years ago
parent
commit
1061d7d7f0
No known key found for this signature in database
GPG Key ID: 6A5D59A3BA48373F
  1. 3
      src/layer.yaml
  2. 2
      src/test-requirements.txt
  3. 5
      src/wheelhouse.txt

3
src/layer.yaml

@ -3,5 +3,4 @@ repo: https://github.com/openstack-charmers/charm-keystone-saml-mellon
options:
basic:
use_venv: True
include_system_packages: True
packages: ['python3-lxml', 'python3-cryptography']
packages: [ 'libffi-dev', 'libssl-dev', 'libxslt1-dev' ]

2
src/test-requirements.txt

@ -6,5 +6,5 @@ stestr>=2.2.0
python-keystoneclient>=1.7.1
python-swiftclient
lxml
git+https://github.com/openstack-charmers/zaza.git@remove-namespaced-tests#egg=zaza;python_version>='3.0'
git+https://github.com/openstack-charmers/zaza.git#egg=zaza
git+https://github.com/openstack-charmers/zaza-openstack-tests.git#egg=zaza.openstack

5
src/wheelhouse.txt

@ -0,0 +1,5 @@
cryptography
lxml
jinja2
psutil
Loading…
Cancel
Save