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: Icd54fc860f354787bfd16da7d47e705523305094
Switch to openstackdocstheme 2.2.1 version. Using
this version 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: I70aec0472ce090cb54855c58f20f4f02e20ae2c2
Make a few cleanups:
- Remove obsolete sections from setup.cfg
- Update requirements, no need for python_version anymore
- Remove install_command from tox.ini, the default is fine.
Change-Id: Iecc1931e93b2254b7b3c95ba1daafd32db204754
Use openstackdocstheme for consistency with all specs displayed on
specs.openstack.org.
This includes updating requirements to current versions, updating specs
building to not publish dirtrees and tread warnings as errors, update
index page, and update settings for the theme.
Change-Id: I905f404361a98d9af1a4ba5c52b8e04acda1688e
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: Iad0076fbf34f699b9eb2134bae623793693534cb
Closes-Bug: #1801657
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: Icbd55a9b4a5c28ce24e7dcd21b37824760430d40
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: I55a899dde06765fb02cc0ff0a17df15e093141c8
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
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
Change-Id: Ia1739a60144bfd3d922ce506dc1277f6958c64e0
Story: #2002586
Task: #24343
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I081601490f339a5dc37a6a5bc597cfc3836bd873
Note also blueprint name is changed from datasource skeleton
generator to datasource scaffold
Implements: blueprint datasource-scaffold
Change-Id: I0e466946273b8df6cc723c99683da818e04f8e07
The Vitrage Dashboard now offers several panels for Entity clicks.
Expand the functionality of these Entity Graphs to add the action
list panel as a click action on Entity. Therefore, the user can check
the available action list based on the setting file configured by the user.
In the list of actions, the user can request an external project for
the Entity, and also enter specific parameter values.
Change-Id: I96f3efd569394de6b94bfebe63803d11d76ab953
Implements: blueprint add-action-list-panel