openstack
/
charm-designate-bind
Code Issues Proposed changes
Juju Charm - Designate Bind Backend
68 Commits 33 Branches 0 Tags 2.1 MiB
Python 100%
Go to file
Ryan Beisner c02395f01c Update functional test definitions 
Change-Id: I8514a108b8b4c7fabcd5d526d4fde56bba4e3574
 		2018-08-27 18:14:28 -05:00
src Update functional test definitions 2018-08-27 18:14:28 -05:00
unit_tests Do not try and download zones for empty url 2018-03-07 12:15:32 +00:00
.bzrignore Initial charm 2016-02-11 10:05:16 +00:00
.gitignore Add unit tests 2016-07-08 12:35:52 +01:00
.gitreview Add .gitreview and clean up repo 2016-07-22 14:53:32 +00:00
.testr.conf Add unit tests 2016-07-08 12:35:52 +01:00
LICENSE Add functional tests 2016-07-13 14:07:13 +00:00
README.md Add .gitreview and clean up repo 2016-07-22 14:53:32 +00:00
rebuild Changed rebuild value to update charms.openstack 2018-08-27 09:48:09 +02:00
requirements.txt Rebuild for application version fix 2017-09-06 21:41:53 +01:00
test-requirements.txt Add .gitreview and clean up repo 2016-07-22 14:53:32 +00:00
tox.ini Merge "Update links in README" 2018-07-12 16:58:55 +00: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