Spec: Add a v2 API endpoint to retrieve the state of different scopes
See "specs/train/add_get_scope_state_api_endpoint.rst" for details. Change-Id: I748ee949a6890b52e2844a51e371a22e40ff18c1 Story: 2005395 Task: 30792
|1 week ago|
|doc/source||1 month ago|
|specs||3 days ago|
|.gitignore||2 years ago|
|.gitreview||1 month ago|
|.zuul.yaml||8 months ago|
|LICENSE||2 years ago|
|README.rst||6 months ago|
|requirements.txt||1 month ago|
|setup.cfg||3 months ago|
|setup.py||2 years ago|
|tox.ini||7 months ago|
This git repository is used to hold approved design specifications for additions to the Cloudkitty 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 story for a given release can be found by looking at the story in Storyboard. Not all stories 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.
For more information about working with gerrit, see:
To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:
tox, the documentation will be available for viewing in HTML format in the