Go to file
Hervé Beraud f6121b5691 Use unittest.mock instead of mock
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.

Note that https://github.com/openstack/charms.openstack is used during tests
and he need `mock`, unfortunatelly it doesn't declare `mock` in its
requirements so it retrieve mock from other charm project (cross dependency).
So we depend on charms.openstack first and when
Ib1ed5b598a52375e29e247db9ab4786df5b6d142 will be merged then CI
will pass without errors.

Depends-On: Ib1ed5b598a52375e29e247db9ab4786df5b6d142
Change-Id: I7b12f467e329e2693e4c7349f328133a1ec3cb00
2021-12-15 10:28:37 +00:00
2019-04-19 19:27:49 +00:00
2021-12-15 10:28:37 +00:00
2016-07-13 14:02:28 +00:00
2021-11-17 14:44:19 -05:00
2021-09-28 18:18:17 +00:00
2021-05-27 06:24:45 -06:00
2021-09-28 18:18:17 +00:00
2021-11-17 14:44:19 -05:00

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

Description
Juju Charm - Designate
Readme 18 MiB
Languages
Python 99.6%
Shell 0.4%