This patch adds processing equivalent to the promote-openstack-specs job to the tacker-spec's Zuul job and fixes the display problem of 2023.2 Specs. Also, change the sphinx extension "sphinxcontrib.plantuml" to "sphinxcontrib.mermaid" to eliminate the dependency on Java in the build environment.  https://specs.openstack.org/openstack/tacker-specs/ Closes-Bug: #2037035 Change-Id: I82a1e549b51669e82d10daaad4378f7a049cf95a
Team and repository tags
OpenStack Tacker Specifications
This git repository is used to hold approved design specifications for additions to the Tacker project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself.
The layout of this repository is:
You can find an example spec in specs/template.rst.
Specifications are proposed for a given release by adding them to the specs/<release> directory and posting it for review. The implementation status of a blueprint for a given release can be found by looking at the blueprint in launchpad. Not all approved blueprints will get fully implemented.
Specifications have to be re-proposed for every release. The review may be quick, but even if something was previously approved, it should be re-reviewed to make sure it still makes sense as written.
Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:
Launchpad blueprints for Tacker can be found at:
For more information about working with gerrit, see:
To validate that the specification is syntactically correct (i.e. get more confidence in the Zuul result), please execute the following command:
tox, the documentation will be available
for viewing in HTML format in the
Please do not checkin the generated HTML files as a part of your
Note that even if a syntax error occurs in
will not be an error in
tox. When using
mermaid to create diagrams, you need to carefully check the
built html file.