97223f60ac
Before the update-status hook would run handlers that are expected to run when the configuration changes or relations added/removed. The update-status hook doesn't hold the machine lock which makes concurrent hook executions possible and seen in the gate where for example multiple "apt-get" executions trying to acquire dpkg's lock. Closes-Bug: #2016893 Change-Id: I63bfd9903057cbea2db8de4f1b612601aacb568d |
||
|---|---|---|
| src | ||
| unit_tests | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| LICENSE | ||
| README.md | ||
| bindep.txt | ||
| build-requirements.txt | ||
| charmcraft.yaml | ||
| metadata.yaml | ||
| osci.yaml | ||
| pip.sh | ||
| rebuild | ||
| rename.sh | ||
| requirements.txt | ||
| test-requirements.txt | ||
| tox.ini | ||
README.md
Overview
This is a "source" charm, which is intended to be strictly the top layer of a built charm. This structure declares that any included layer assets are not intended to be consumed as a layer from a functional or design standpoint.
Test and Build
Building, pushing and publishing to the charm store is automated by CI to ensure consistent flow. Manually building is useful for development and testing, however.
tox -e pep8
tox -e py37
tox -e build
Contact Information
OFTC IRC: #openstack-charms