openstack
/
charm-designate-bind
Code Issues Proposed changes
Juju Charm - Designate Bind Backend
37 Commits 33 Branches 0 Tags 2 MiB
Python 100%
Go to file
Ryan Beisner 4d2101b684 Add Artful dev series metadata 
Change-Id: I8900577abe3c34288be1942dcf0e2c6bb5ca980d
 		2017-09-26 14:04:57 -04:00
src Add Artful dev series metadata 2017-09-26 14:04:57 -04:00
unit_tests Use charms.openstack charmhelpers test_mocks 2017-05-25 11:03:15 +01: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 Rebuild for application version fix 2017-09-06 21:41:53 +01: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 Update tox.ini for py27 requirement 2016-11-28 18:21:12 -06: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