These were missed in change I3eafc92ba7c7305b1a73d3f96c427ed12c96dbf7.
Change-Id: Idf7148bcf588efbd20352bf2160ecee573156444
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
check_policy_json() common check need [oslo_policy].policy_file
config value and it is better to register those options explicitly
in check_policy_json() in case they are not register by services.
Currently it work as oslo.policy opts are registered via some import
in service side code path for upgradechecks which are not so safe
when these code import path change.
Change-Id: I16fcce119698c7375e4b58558fdce89e78a79a9b
oslotest 1.5.1 is restricted to pbr <1.0 which conflict
with other deps lower constarint for pbr.
Error:
The conflict is caused by:
oslo-i18n 3.15.3 depends on pbr!=2.1.0 and >=2.0.0
oslo-serialization 2.21.1 depends on pbr!=2.1.0 and >=2.0.0
oslo-utils 4.5.0 depends on pbr!=2.1.0 and >=2.0.0
oslotest 1.5.1 depends on pbr!=0.7, <1.0 and >=0.6
https: //zuul.opendev.org/t/openstack/build/cb2bce3b4e004601958b764dfd0737b8
Change-Id: I513262b85a57ce9f81a63bd778fdd7f7be27e485
As part of community goal[1] for migrating the policy file
from JSON format to YAML we need to add upgrade check to
detect any JSON formatted file. That check needs to be
done in each service side which are deprecating the JSON
format. So to avoid duplicate code, this commit add that
check in oslo_upgradechecks and that can be enabled from
service side during they migrate to YAML format.
Service will enable it like below:
_upgrade_checks = (
(_('Policy File JSON to YAML Migration'),
(common_checks.check_policy_json, {'conf': CONF})),
)
Also modify the check() method to accept the **kwargs for checks.
[1] https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: Ifa71c20879c964f794a40b981744d95db4ab1602
Switch to openstackdocstheme 2.2.0 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.
Remove docs requirements from lower-constraints, they are not needed
during install or test but only for docs building.
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.
Depends-On: https://review.opendev.org/728938
Change-Id: Iec4e4b3ed18e36d8ee1942e45e290ce292e7f881
Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
Change-Id: I2831ab17d943638062b709882c7a1cc481e46476
Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.
Change-Id: Ic626d2dc2974ac6ac7b6a816963995915e723ec7
No reason to still be using oslo.sphinx in this day and age.
Change-Id: I7734f9a636b5435f70659f8bd3d0c2b7e49c78d6
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Stephen Finucane