c973c8fe70
It's currently possible to disable the trusts API and trusts are therefore essentially an API extension and not a first-class member of the keystone API. By now, trusts are a widely-used feature and are essential for services like Heat. Allowing optional APIs is an interoperability nightmare that we should discourage. This patch marks the config flag to enable trusts as deprecated so that in the future it will not be possible to disable it. bp deprecated-as-of-queens Change-Id: Iac454ddf7878b8f2705e7abb44181f1a19af015f
21 lines
1.1 KiB
YAML
21 lines
1.1 KiB
YAML
---
|
|
deprecations:
|
|
- >
|
|
The ``/OS-FEDERATION/projects`` and ``/OS-FEDERATION/domains`` APIs are
|
|
deprecated in favor of the ``/v3/auth/projects`` and ``/v3/auth/domains``
|
|
APIs. These APIs were originally marked as deprecated during the Juno
|
|
release cycle, but we never deprecated using ``versionutils`` from oslo.
|
|
More information regarding this deprecation can be found in the `patch
|
|
<https://review.openstack.org/#/c/115423/>`_ that proposed the deprecation.
|
|
- >
|
|
[`bug 1728690 <https://bugs.launchpad.net/keystone/+bug/1728690>`_]
|
|
The ``member_role_id`` and ``member_role_name`` config options were used to
|
|
create a default member role for keystone v2 role assignments, but with the
|
|
removal of the v2 API it is no longer necessary to create this default
|
|
role. This option is deprecated and will be removed in the S release. If
|
|
you are depending on having a predictable role name and ID for this member
|
|
role you will need to update your tooling.
|
|
- >
|
|
The ``enabled`` config option of the ``trust`` feature is deprecated and
|
|
will be removed in the next release. Trusts will then always be enabled.
|