openstack
/
charm-designate
Code Issues Proposed changes
Juju Charm - Designate
170 Commits 33 Branches 0 Tags 17 MiB
Python 99.6%
Shell 0.4%
Go to file
Doug Hellmann 679caae18f import zuul job settings from project-config 
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: I3d68694a8ab036c57bb810e6a837e8186fe1d6b9
Story: #2002586
Task: #24317
 		2018-09-11 13:08:55 -04:00
src Merge "Adding designate worker and producer to Rocky" 2018-08-30 19:01:06 +00:00
unit_tests Add "also-notifies" option 2018-03-26 10:22:09 +02: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 Changed rebuild value to update charms.openstack 2018-08-27 09:58:19 +02:00
requirements.txt Render configs always needs the cluster relation 2016-07-27 15:24:14 +00:00
test-requirements.txt Add .gitreview and clean up repo 2016-07-22 12:01:10 +00:00
tox.ini Add py36 testenv 2018-07-12 15:53:39 +07: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