charm-designate-bind:stable/2023.1

Last commit made on 2023-06-08
Get this branch:
git clone -b stable/2023.1 https://git.launchpad.net/charm-designate-bind

Branch merges

Branch information

Name:
stable/2023.1
Repository:
lp:charm-designate-bind

Recent commits

8fed2f9... by Felipe Reyes

Bump up Charm-helpers revision

Update src/build.lock to get the latest revision available in the
stable/antelope branch, among the most relevant patches are:

837a8b58 Support legacy cert requests (#799)
580c7764 Update Makefile to be consistent with CI (#777) (#795)
a2468260 Run CI on stable branches (#786) (#787)
ed014373 Update method for checking endpoint protocol (#769) (#775)

Change-Id: I1fe338fb40b647b4d4f4bb424e315d46e093e97e

fdc6f63... by Zuul <email address hidden>

Merge "Stable artefacts for stable/2023.1 (antelope)" into stable/2023.1

61c195b... by Alex Kavanagh

Stable artefacts for stable/2023.1 (antelope)

This patch is to lock the stable/2023.1 (antelope release) charms
down so that as much as possible.
In particular, this patch does:

- set the .gitreview to stable/2023.1
- lock zaza and zaza-openstack-tests to stable/antelope branches
- for reactive charms Add build.lock files to lock the layers
  and python modules used to build the charm.
- for ops framework charms, extract a pip freeze from the
  charmcraft container after building the charm to lock the
  modules used to build the charm.
- drop the kinetic bundles if the exist. (Note the updates to
  tests.yaml is in another batch (topic: antelope-voting)
- update the bundles so that they point to the antelope specific
  channels. e.g. 2023.1/edge for OpenStack charms, 23.03/edge for
  OVN charms, quincy/edge for Ceph charms and generally, the
  appropriate LTS Jammy branch for the various support charms.

Change-Id: I25c9965194f41fcd254fe9e6442ee476010d035c

ceda136... by Corey Bryant

Enable jammy-antelope voting and drop kinetic-zed tests

* Voting was turned on for jammy-antelope in the
  project-template for charm-functional-jobs in zosci-config
* Voting for jammy-antelope bundles with non-standard names
  is turned on in individual charms
* Kinetic-zed bundles/tests are removed

Change-Id: I08d5503b3d49f35c812c5e503e8775e8b27044ce
(cherry picked from commit 76088020aa2e3fd0bcab12f2997e797b9f0d873f)

d4578a8... by Corey Bryant

Add Antelope support

* sync charm-helpers to classic charms
* change openstack-origin/source default to antelope
* align testing with antelope
* add new antelope bundles
* add antelope bundles to tests.yaml
* add antelope tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases

Change-Id: Ib717ac6e3e82972b67bf89d1603176127eb1e5ec

f333750... by Liam Young

Fix charm for tox4 compatibility

Related-Bug: 2002788
Change-Id: I210cc3cd05f8f02d170a6b273aefcba51d0740f0

490a302... by Felipe Reyes

Drop 'source' config key from support charms

- mysql-innodb-cluster
- rabbitmq-server

Change-Id: I1a009cd083a22ba86ba2fd4aec660d7729a283f7
Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/970

ca2f0a4... by Corey Bryant

Fix s390x and pp64el builds

Without this change s390x and pp64el fail to build cryptography.

Change-Id: Id831b255f755b7a0e4acda0a2623aabe31e52ac6

57539ec... by Corey Bryant

Build separately for each supported series and use binary builds

Charms for OpenStack Yoga supports both Ubuntu Focal and Jammy
which means Python 3.8 and Python 3.10. Managing dependencies
across those two versions is non-trivial and we need to build
the charm on the series the charm is supposed to support.

Switch to using a binary build which allows pip's dependency
resolution to work.

Change-Id: If7ccdcaa900a3276c6e8eb124cdb0f605b20d6c3

c2c174f... by Corey Bryant

Add Kinetic and Zed support

* sync charm-helpers to classic charms
* change openstack-origin/source default to zed
* align testing with zed
* add new zed bundles
* add zed bundles to tests.yaml
* add zed tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases
* add bindep.txt for py310
* sync tox.ini and requirements.txt for ruamel
* use charmcraft_channel 2.0/stable
* drop reactive plugin overrides
* move interface/layer env vars to charmcraft.yaml

Change-Id: I2c98ab0f82aa6d6d0a43365cee04d6da34a39ce4