Juju Charm - Designate Bind Backend
Go to file
Alex Kavanagh 315db68d18 Remove Jinja2/MarkupSafe from wheelhouse.txt
These were pins to cope with supporting python 3.4.  However,
layer-basic (as of [1]) now does the right thing in terms of getting the
correct versions of Jinja2 and MarkupSafe for the version of Ubuntu that
the charm is being built on:

1 - https://github.com/juju-solutions/layer-basic/pull/199

Change-Id: I29533d4794d6fb0e045893c934cb4920cacb408e
2022-07-08 11:37:04 +01:00
src Remove Jinja2/MarkupSafe from wheelhouse.txt 2022-07-08 11:37:04 +01:00
unit_tests Add functionality to configure virtual service IPs 2022-04-12 13:46:23 -07:00
.bzrignore Initial charm 2016-02-11 10:05:16 +00:00
.gitignore Updates to enable jammy and finalise charmcraft builds 2022-04-08 12:30:57 -04: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 Updates to enable jammy and finalise charmcraft builds 2022-04-08 12:30:57 -04: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
build-requirements.txt Update to build using charmcraft 2022-02-01 19:57:43 +00:00
charmcraft.yaml Updates to enable jammy and finalise charmcraft builds 2022-04-08 12:30:57 -04:00
metadata.yaml Migrate charm to charmhub latest/edge track 2022-01-27 20:13:16 +00:00
osci.yaml Updates to enable jammy and finalise charmcraft builds 2022-04-08 12:30:57 -04:00
pip.sh Add xena bundles 2021-10-05 13:37:34 +01:00
rebuild Add xena bundles 2021-10-05 13:37:34 +01:00
rename.sh Update to build using charmcraft 2022-02-01 19:57:43 +00:00
requirements.txt Updates to enable jammy and finalise charmcraft builds 2022-04-08 12:30:57 -04:00
test-requirements.txt Update to build using charmcraft 2022-02-01 19:57:43 +00:00
tox.ini Updates to enable jammy and finalise charmcraft builds 2022-04-08 12:30:57 -04: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