openstack
/
charm-designate-bind
Code Issues Proposed changes
Juju Charm - Designate Bind Backend
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
152 Commits
20 Branches
0 Tags
1.2 MiB
 
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Alex Kavanagh f8986150ab
Add xena bundles 		4 weeks ago
src Add xena bundles 2 weeks ago
unit_tests Fix charm so that on focal it uses named service 5 months ago
.bzrignore Initial charm 6 years ago
.gitignore Fix unit tests after charms.openstack update 3 years ago
.gitreview OpenDev Migration Patch 3 years ago
.stestr.conf Replace ostestr with stestr in testing framework. 3 years ago
.zuul.yaml Switch to Ussuri jobs 2 years ago
LICENSE Add functional tests 5 years ago
README.md Moving to OFTC 5 months ago
osci.yaml Add xena bundles 2 weeks ago
pip.sh Add xena bundles 2 weeks ago
rebuild Add xena bundles 2 weeks ago
requirements.txt Sync release-tools 3 months ago
test-requirements.txt Sync release-tools 3 months ago
tox.ini Add xena bundles 2 weeks ago

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

OFTC IRC: #openstack-charms