Juju Charm - Designate
Go to file
James Page 53c204a796 Drop use of 'amqp.requested-access' flag
In an amqp relation is removed and re-added, the charm won't
make a new request for access.  As the handler simply sets two
data items on the relation, avoid the use of the requested-access
flag.

Change-Id: Ibbffabe277adacf966443bae04a6a64a07964261
Closes-Bug: 1784076
2018-11-27 13:59:06 +00:00
src Drop use of 'amqp.requested-access' flag 2018-11-27 13:59:06 +00:00
unit_tests Drop use of 'amqp.requested-access' flag 2018-11-27 13:59:06 +00:00
.gitignore Enable designate to list on all interfaces 2017-11-29 11:58:36 +00:00
.gitreview Add .gitreview and clean up repo 2016-07-22 12:01:10 +00:00
.testr.conf Unit tests and lint fixes 2016-07-07 09:36:22 +01:00
.zuul.yaml import zuul job settings from project-config 2018-09-11 13:08:55 -04:00
LICENSE Add License info 2016-07-13 14:02:28 +00:00
README.md Add .gitreview and clean up repo 2016-07-22 12:01:10 +00:00
rebuild Rebuild for sync charm-helpers 2018-11-07 15:42:49 -06:00
requirements.txt Update requirements 2018-10-04 10:51:40 -05:00
test-requirements.txt Update requirements 2018-10-04 10:51:40 -05:00
tox.ini fix tox python3 overrides 2018-09-26 18:37:59 -04:00

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

Freenode IRC: #openstack-charms