Python 3.8 was removed from the tested runtimes for 2024.2[1] and has
not been tested since then.
Also add Python 3.12 which is part of the tested runtimes for 2025.1.
Now unit tests job with Python 3.12 is voting.
[1] https://governance.openstack.org/tc/reference/runtimes/2024.2.html
Change-Id: I69fdd7d996668f8f2b75a810b8c3d5c2d8f6ea3f
As per the current release tested runtime, we test
python version from 3.8 to 3.11 so updating the
same in python classifier in setup.cfg
Change-Id: I76d2682e4c3dae9ed9bf0742f9850c84d8b34468
The api_doc_dir option and the autodoc_index_modules option were both
deprecated in pbr 4.2.
The required options for the sphinxcontrib-apidoc extension are already
defined in doc/source/conf.py .
Change-Id: Id1f59c0be87ae10e2cf3fc05cd8b6f561eeccd85
These translation sections are not needed anymore, Babel can
generate translation files without them.
Remove babel.cfg as well, this is the default role and not needed
anymore.
also remove Babel from requirements[1]
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014227.html
Change-Id: I0de45b0ced44fc0b4110b42912ab7682f243aaa2
Since setuptools v54.1.0[1], the parmeters with dash have been
deprecated in favor of the new parameters with underscore.
This change updates the parameters accordingly to avoid the warnings
like the example below.
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: I0335bf0e7382597abddc0cadd6fc49775ad1396e
Now that we are running the Victoria tests that include a
voting py38, we can now add the Python 3.8 metadata to the
package information to reflect that support.
Change-Id: I49640c50a7b78212a5c2ad03acb43be7adf98305
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete section from setup.cfg: Wheel is not needed for
python 3 only repo
- Update requirements, no need for python_version anymore
- Remove future import from doc/source/conf.py
Change-Id: Ibf594171cea8f81cc4139b29cbdce54f6d5107a7
Python 3.5 was the target runtime for the Rocky release.
The current target py3 runtime for Stein is Python 3.6,
so there is no reason to keep testing against the older version. Also
correct setup.cfg and tox.ini to reflect the current supported Python
versions.
https://governance.openstack.org/tc/reference/runtimes/stein.html#python-runtime-for-stein
Change-Id: I67c892e0b5afaf8e603a77102e06567a1bfe2eb6
This change removes the unused "warnerrors" setting that
was part of [pbr], which was replaced by "warning-is-error"
in sphinx 1.5 and above[0]. This also fixes any warnings
and errors that came up when running `tox -edocs` using
this new feature:
- Specified correct instance of 'List'
This change also adds the "warning-is-error" setting
to setup.cfg in order to allow for strict doc validation
which will cause doc building to fail if any warnings
are thrown.
[0] http://lists.openstack.org/pipermail/openstack-dev/2017-March/113085.html
Change-Id: I8111193e5a1ae7d063ab4cc37186aea1299964a4
The openstack.org pages now support https and our references to
the site should by default be one signed by the organization.
Change-Id: Ia6cdaf7fabd1c355df002aa07b0695610dde9cd1
Now that there exists only a gate job for Python 3.5 and not 3.4,
we should remove those references to the 3.4 that is untested.
Change-Id: Id32fca50f5f1834175b6003be61f2cc4c8b9aeeb
the CLI has been deprecated for a long time, and many docs and
install guides recommend using OSC instead of `keystone`.
- removes CLI
- removes man page from docs
- removes CLI tests
- removes `bootstrap` from contrib
- removes entrypoint from setup.cfg
implements bp: remove-cli
Change-Id: Icbe15814bc4faf33f513f9654440068795eae807
Follow new infra setup for translations, see spec
http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html
for full details.
This basically renames
python-keystoneclient/locale/python-keystoneclient.pot to
keystoneclient/locale/keystoneclient.pot. For this we need to update
setup.cfg. The domain name is already correct in keystoneclient/_i18n.py.
The project has no translations currently, let's remove the outdated
pot file, the updated scripts work without them. So, we can just
delete the file and once there are translations, an updated pot file
together with translations can be imported automatically.
Change-Id: Ie5a0c3e8fcdb485edf05f2188fce64a9fce96b5f
The .pot file was named incorrectly and in the wrong location so the
traslations were not getting generated.
Change-Id: Iafd2b7f06dd840fa0505729a9fc898e7e281c50c
Closes-Bug: 1493484
When bootstrapping a cloud, using this auth plugin is necessary to be
able to provide an admin token. However, there has been some confusion
as to its officialness and the names of its parameters. Make it clear
why it's exposed, and additionally be clearer about squatting on the
name of the plugin so that things can depend on its interface.
Change-Id: I8e896b28d5879cd4b1372009926c67cde773308f
The setup.cfg refers to Programming Language of Python 3.3 whereas
jenkins is setup only to test Python 3.4. This patch updates setup.cfg
and removes py33 from tox.ini.
TrivialFix
Change-Id: I1bc7fae6481c4fef71746ed1c144af37445a81ac
This patch allows a federated user to obtain an unscoped token by
providing login credentials for a keystone identity provider.
The current implementation should work with any properly configured
openid connect provider.
partially implements bp openid-connect
Change-Id: Iade52b5c1432d64582cbaa8bac41ac6366c210f9
Don't build API documentation for the keystoneclient tests.
These are not public functions, pollute the existing docs, and extend
the time required to build docs.
A re-implementation of be1e94f
Change-Id: Ib0e91ebfe4234bc3332b7c3051dba98248312a34
A temporary fix was added to get around a bug in how pbr handles
its autodoc_tree_index_modules setting. Since this bug is fixed we no
longer need the work around.
Change-Id: Id8274ef5c244bf50a34702ed9b4e50d3b82d8028
Closes-Bug: #1260495
Authentication workflow for the Active Directory Federated Services
(ADFS) by Microsoft is different from 'standard' ECP based one.
This plugin allows for authentication and fetching security token with SAML2
assertion inside, sending to the Service Provide and retrieving an
unscoped token.
Change-Id: I588de1967a7fb92c5928686d092895847553923a
Implements: blueprint add-saml2-cli-authentication
A Framework for creating plugins that work across identity versions.
Upon creating a generic plugin the plugin will go and discover what
versions are available on the server and then attemp to construct a
suitable plugin.
Blueprint: version-independant-plugins
Change-Id: If7fed94aaf4636e80a9c3a834cf6c5430f20e489
Since Patch https://review.openstack.org/#/c/107231/ was abandoned and
entry ``v3unscopedsaml`` stays in the setup.cfg, there should
also some room for v3scopedsaml entry which lets users scope their
unscoped tokens.
Change-Id: Ie42206c323d287b905b4c5da9c790e544a8b8433
Auth plugin authenticating against remote SAML based Identity Providers.
Upon successful authentication the plugin retrieves and stores unscoped token.
Plugin object should be later used for scoping the token.
Currently only HTTP BasicAuth Method is supported as
an IdP authn method.
Will not work for ADFS, as that has extensions to the document formats
as well as a different workflow.
Change-Id: Ieea40505a406bedf7219fa6f9e6cf29a45ad6e88
Implements: blueprint add-saml2-cli-authentication
Provide a pattern for auth plugins to load themselves from a config
object. The first user of this will be auth_token middleware however it
is not likely to be the only user.
By doing this in an exportable way we are defining a single config file
format for specifying how to load a plugin for all services. We also
provide a standard way of retrieving a plugins options for loading via
other mechanisms.
Blueprint: standard-client-params
Change-Id: I353b26a1ffc04a20666e76f5bd2f1e6d7c19a22d
To better facilitate the building and publishing of sphinx
documentation by Jenkins we are moving all openstack projects with
sphinx documentation to a common doc tree structure. Documentation
goes in project/doc/source and build results go in project/doc/build.
Change-Id: I205e8bb1ddf6dae1d7392b32975319c6a6d98673
