openstack
/
charm-designate
Code Issues Proposed changes
Juju Charm - Designate
319 Commits 33 Branches 0 Tags 17 MiB
Python 99.6%
Shell 0.4%
Go to file
David Negreira b5b4d600bd separate rndc.key file per application 
This change fixes an issue that when the charm-designate is
related to two different designate-bind applications, the same
rndc key file is used for the two different applications.

We fix this by writing an rndc_key_file per application rather than in
a single rndc.key file for all the units.

Closes-Bug: #1995975

Change-Id: I5dafeb2b4dcf9549260081d3674038f836d29f0f
Signed-off-by: David Negreira <david.negreira@canonical.com>
 		2024-03-27 14:03:39 +00:00
src separate rndc.key file per application 2024-03-27 14:03:39 +00:00
unit_tests separate rndc.key file per application 2024-03-27 14:03:39 +00:00
.gitignore Add *.charm to gitignore 2022-04-18 21:06:24 +01:00
.gitreview Stable artefacts for stable/2023.1 (antelope) 2023-04-20 19:00:31 +01:00
.stestr.conf Replace ostestr with stestr in testing framework. 2019-03-07 17:11:03 -05:00
.zuul.yaml Add Antelope support 2023-03-08 15:53:06 +00:00
LICENSE Add License info 2016-07-13 14:02:28 +00:00
README.md Moving to OFTC 2021-05-27 06:24:45 -06:00
bindep.txt Add Kinetic and Zed support 2022-08-31 19:57:31 +01:00
charmcraft.yaml [2023.1] Ensure get_requests_for_local_unit doesn't fail on incomplete relation 2023-08-17 10:25:48 +00:00
metadata.yaml Migrate charm to charmhub latest/edge track 2022-01-27 20:12:03 +00:00
osci.yaml Add Antelope support 2023-03-08 15:53:06 +00:00
rebuild [2023.1] Ensure get_requests_for_local_unit doesn't fail on incomplete relation 2023-08-17 10:25:48 +00:00
rename.sh Update to build using charmcraft 2022-02-01 19:55:42 +00:00
requirements.txt Add Kinetic and Zed support 2022-08-31 19:57:31 +01:00
test-requirements.txt Stable artefacts for stable/2023.1 (antelope) 2023-04-20 19:00:31 +01:00
tox.ini Fix charm for tox4 compatibility 2023-01-17 14:56:01 +00: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