73a39d4c14
Add the 'docs' key and point it at a Discourse topic previously populated with the charm's README contents. When the new charm revision is released to the Charmhub, this Discourse-based content will be displayed there. In the absense of the this new key, the Charmhub's default behaviour is to display the value of the charm's 'description' key. Change-Id: I2836aadfe6b9a035c6838b144e3f65436e4c184e |
||
|---|---|---|
| src | ||
| unit_tests | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| LICENSE | ||
| README.md | ||
| bindep.txt | ||
| charmcraft.yaml | ||
| metadata.yaml | ||
| osci.yaml | ||
| 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 py34 # or py27 or py35
tox -e build
Contact Information
OFTC IRC: #openstack-charms