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: I7ac3d0bd3eabbf1c23a5060b9f91b8a6c44336be
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: Iac415cd5bd7346847edeb174b059ffbc3e2a1bdf
Make a few cleanups:
- Remove obsolete sections from setup.cfg
- Remove install_command from tox.ini, the default
is fine
- Switch to sphinx-build
- Enable warnings for doc build, fix all warnings
- Remove git handling from conf.py, openstackdocstheme does this now
- Cleanup tox.ini
Change-Id: I51796be20596afc2305c2d8ea189b4037bd28b2d
Updated to remove leftover copy/paste references to Nova, as well
as our use of Storyboard instead of Launchpad.
Change-Id: Ie4c3d86eb4751151409006c817e4da7524d7e39a
The docs target in tox was failing because it was still using
oslosphinx. This patch replaces it with openstackdocstheme.
Change-Id: I4b6a93a306441f25d333889eaab3e9bbab3974c6
Story: 2005767
Task: 33481
The commands used by constraints need at least tox 2.0. Update to
reflect reality, which should help with local running of constraints
targets.
Change-Id: Idd54092b2d2b9713d4ffbc2bcbd87a0f222d8a23
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Remove stein from toc, there's no spec yet and zuul complains about an
empty toc.
Change-Id: Iede70fc477d0fe7b0b63336d1e120d5d5c23160d
Story: #2002586
Task: #24285
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: Id94e8d7db17059228e8957e74922a684043ed469
- Listed out detail work items in the specification document.
- Listed out detail primary assignee.
- Added assert "assert:supports-rolling-upgrade" tag for Barbican
Change-Id: If758e84b6aa9a86de46ce405d8e174ca56c76723
When we run "tox" command, there are two
redundancy files named AUTHORS and ChangeLog.
They should be ignored.
Change-Id: Ia49bbe32f32054365f6380709edf55083693b019
Instead of pointing to openstack.org, the homepage has been
changed to point to the homepage of barbican-specs.
Change-Id: Id245b7cd693b0fbebdceb809a93c7ebeb5ebde5d
Updated patch to clarify review comments and correct typos.
Added details around plugin name and how its used in secret_stores
'name' field.
Added changes related to how multiple plugin configuration is going to
be specified and used.
Added field to capture crypto_plugin name in addition to secret store plugin
name. This is done as both software only and pkcs11 plugin uses database
(store_crypto) as storage backend. Difference is in crypto plugin used
(simple crypto vs p11_crypto).
APIImpact
SecurityImpact
Change-Id: I02054d80f68f38145b399909d60db80a4d91c1ba
The blueprint for this feature was approved in the Liberty cycle.
However, the feature was not implemented. This CR proposes a slightly
modified blueprint for the Newton cycle.
Change-Id: I6b27c7b2b73c429b53bd235b46f7ea753166406a