python-designateclient 4.5.1 release

meta:version: 4.5.1
meta:diff-start: -
meta:series: yoga
meta:release-type: release
meta:pypi: yes
meta:first: no
meta:release:Author: Michael Johnson <johnsomor@gmail.com>
meta:release:Commit: Michael Johnson <johnsomor@gmail.com>
meta:release:Change-Id: I9e21438534a0f449ce0599d2e96010fc772d8a01
meta:release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta:release:Code-Review+2: Thierry Carrez <thierry@openstack.org>
meta:release:Workflow+1: Thierry Carrez <thierry@openstack.org>

The zone transfer request set command was missing the
--target-project-id option so you cannot change the target project ID of
a zone transfer request after creation with the CLI.
This option is supported by the API and documented in the API reference
guide.
This patch adds this option.

Closes-Bug: #1977625
Change-Id: Idd570a5aef57c06971db2450fdfb823cf0c07bfd
(cherry picked from commit fba1354e)

Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.

Until the requirements repository has as stable/yoga branch, tests will
continue to use the upper-constraints list on master.

Change-Id: I9663f1e32d548aef4f207cebc234f1170e86080e

Change-Id: I04d44e74be098ec02c10306ccdb881db6635435a

python-designateclient 4.5.0 release

meta:version: 4.5.0
meta:diff-start: -
meta:series: yoga
meta:release-type: release
meta:pypi: yes
meta:first: no
meta:release:Author: Elod Illes <elod.illes@est.tech>
meta:release:Commit: Elod Illes <elod.illes@est.tech>
meta:release:Change-Id: I4bb03dcc41c3a9deb9a59843a7cc58731528084a
meta:release:Code-Review+1: Michael Johnson <johnsomor@gmail.com>
meta:release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
meta:release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta:release:Workflow+1: Elod Illes <elod.illes@est.tech>

To be able to create profiling traces for Designate, client should
be able to send special HTTP header that contains trace info.

Don't worry no security issue here, trace information is signed by HMAC
key that is setted in api-paste.ini. So only person that knows HMAC key
is able to send proper header.

Main patch (in Designate) is:
https://review.opendev.org/c/openstack/designate/+/773574

Change-Id: I4b84ac1a5d4f84da3a38e4e0cb0990a54c6044ef

Yoga testing runtime[1] has been updated to add py39
testing as voting. Unit tests update are handled by the
job template change in openstack-zuul-job

- https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/820286

this commit updates the classifier in setup.cfg file.

[1] https://governance.openstack.org/tc/reference/runtimes/yoga.html

Change-Id: Id58e9e9532c593a211acea497f5928c3689ac333

We currently have no unit test coverage for the
cli (openstack) implementation. This adds some very
basic coverage that we can later expand upon.

Change-Id: Ibf06cfcbf4f7c12957cf5aa0ba8de66e0554f4d0

This patch adds the Designate hacking checks to also run against
the Designate client code to maintain consistent style
checking across the Designate repositories.

It also resolves one style check failure.

Change-Id: I09786482b2e7fecaa3d4484c9b1a017fae04cfea

--edit-managed sets a header x-designate-edit-managed-records
that indicates the current request wishes to modify managed records
such as the SOA or NS record created for a zone. This is only used
by the recordset update and delete API methods so can be removed
elsewhere.

Closes-Bug: 1928411

Change-Id: I18bfdae045c8b5e589075865eb024cee4852d8f9

Moving on py3 as the default runtime for tox to avoid to update
this at each new cycle.

Change-Id: If96047f90eaddf313534d9a9652d665ff26b206a

Previous versions of jsonschema (<3.2.0) doesn't support python 3.8 [1].
Python 3.8 is part of the victoria supported runtimes [2] so we now force
to use jsonschema version 3.2.0 to avoid issues, remove ambiguity and ensure
that everything works with python 3 in general.

This patch also advances tempest to 25.0.0 and oslo.concurrency to 3.26.0
for proper python3 support.

[1] https://github.com/Julian/jsonschema/pull/627
[2] https://governance.openstack.org/tc/reference/runtimes/victoria.html#python-runtimes-for-victoria

Change-Id: Iaf5ff97322ff6f18a3693dead20ec8f6fe7561ad

H402 hacking have been removed since hacking 0.10.
So remove H402 ignore statement.

Change-Id: I6de537410bd1d8b320d3c9db603ae1669a4faf25

The __future__ module [1] was used in this context to ensure compatibility
between python 2 and python 3.

We previously dropped the support of python 2.7 [2] and now we only support
python 3 so we don't need to continue to use this module and the imports
listed below.

Imports commonly used and their related PEPs:
- `division` is related to PEP 238 [3]
- `print_function` is related to PEP 3105 [4]
- `unicode_literals` is related to PEP 3112 [5]
- `with_statement` is related to PEP 343 [6]
- `absolute_import` is related to PEP 328 [7]

[1] https://docs.python.org/3/library/__future__.html
[2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
[3] https://www.python.org/dev/peps/pep-0238
[4] https://www.python.org/dev/peps/pep-3105
[5] https://www.python.org/dev/peps/pep-3112
[6] https://www.python.org/dev/peps/pep-0343
[7] https://www.python.org/dev/peps/pep-0328

Change-Id: I3dadeaa3242d0b55ba891a8eb4abb199a8d2468b

We had a question about whether the TLD name could be used as the
"id" positional argument when show/set/delete a TLD.
This patch clarifies that names or IDs will work with those commands
in the OpenStack client.

Change-Id: I93952596f3c82ae37d903a8ea4dd8700ae8fc314

This patch bumps the lower-constraint for decorator to 4.2.1
to resolve a setuptools incompatibility with the usage of 2to3 in
decorator < 4.0.0. Version 4.2.1 of decorator is currently the
packaged version included in centos 8/stream.

Change-Id: Ib74fd9ebbea7496fd3e7f453e618b218f8859f6f

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for yoga.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I83e826787e18cdf30e3788da3f1c2df15f1e61e2

Add file to the reno documentation build to show release notes for
stable/xena.

Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/xena.

Sem-Ver: feature
Change-Id: Id0e1d24bdceaf9f5a4d5dac7aa634b4c8d21e828

python-designateclient 4.3.0 release

meta:version: 4.3.0
meta:diff-start: -
meta:series: xena
meta:release-type: release
meta:pypi: yes
meta:first: yes
meta:release:Author: Hervé Beraud <hberaud@redhat.com>
meta:release:Commit: Hervé Beraud <hberaud@redhat.com>
meta:release:Change-Id: I845d699e26cfff3d63e8c588a64202c92736824f
meta:release:Code-Review+1: Michael Johnson <johnsomor@gmail.com>
meta:release:Code-Review+2: Thierry Carrez <thierry@openstack.org>
meta:release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
meta:release:Workflow+1: Hervé Beraud <herveberaud.pro@gmail.com>

Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:

  UserWarning: Usage of dash-separated 'description-file' will not be
  supported in future versions. Please use the underscore name
  'description_file' instead

[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb

Change-Id: I2447dd697d0282c22cbadc775b87df186e46bf42

This patch removes the use of "six" as the package declares only
python3 support.
It also updates the appdirs lower-constraint to 1.4.0 to support
pip. This version is available on both centos8 and focal.
It also removes the linter related packages from lower-constraints.

Change-Id: I9337f1998749bc40737f2f0e2dcc406b6f3a0ddf

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for xena.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I0f54a3b753137e6dbc5ea0c3a77886ad622422d7