Juju Charm - Designate
ab565c71bd
This change fixes an issue that when the charm-designate is related to two different designate-bind applications, the same rndc key file is used for the two different applications. We fix this by writing an rndc_key_file per application rather than in a single rndc.key file for all the units. Closes-Bug: #1995975 Change-Id: I5dafeb2b4dcf9549260081d3674038f836d29f0f Signed-off-by: David Negreira <david.negreira@canonical.com> |
||
---|---|---|
src | ||
unit_tests | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
bindep.txt | ||
charmcraft.yaml | ||
LICENSE | ||
metadata.yaml | ||
osci.yaml | ||
README.md | ||
rebuild | ||
rename.sh | ||
requirements.txt | ||
test-requirements.txt | ||
tox.ini |
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