openstack
/
charm-designate-bind
Code Issues Proposed changes
Juju Charm - Designate Bind Backend
151 Commits 33 Branches 0 Tags 2.1 MiB
Python 100%
Go to file
Aurelien Lourot cfa81adfde Sync release-tools 
In order to fix ResolutionImpossible on tox invocation.

https://github.com/openstack-charmers/release-tools/issues/151
https://github.com/openstack-charmers/release-tools/pull/152

Change-Id: Ib0398e33f2c629208ccf7f3323ad92626d791942
 		2021-07-22 14:53:58 +02:00
src Sync release-tools 2021-07-22 14:53:58 +02:00
unit_tests Fix charm so that on focal it uses named service 2021-06-02 10:53:00 +01:00
.bzrignore Initial charm 2016-02-11 10:05:16 +00:00
.gitignore Fix unit tests after charms.openstack update 2018-10-23 13:49:40 +02:00
.gitreview OpenDev Migration Patch 2019-04-19 19:36:36 +00:00
.stestr.conf Replace ostestr with stestr in testing framework. 2019-03-07 17:11:09 -05:00
.zuul.yaml Switch to Ussuri jobs 2019-12-26 18:14:34 +08:00
LICENSE Add functional tests 2016-07-13 14:07:13 +00:00
README.md Moving to OFTC 2021-05-27 06:25:26 -06:00
osci.yaml Test bundles for focal-wallaby and hirsute-wallaby 2021-05-06 09:56:20 +00:00
rebuild rebuild - restore c-h proxy env vars for add-apt-repository 2021-05-13 09:08:50 -04:00
requirements.txt Sync release-tools 2021-07-22 14:53:58 +02:00
test-requirements.txt Sync release-tools 2021-07-22 14:53:58 +02:00
tox.ini Sync release-tools 2021-07-22 14:53:58 +02: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

OFTC IRC: #openstack-charms