cinder/api-ref/source/v2/volumes-v2-extensions.inc
Sean McGinnis 2e5a91da72 Use rest_status_code for api-ref response codes
Rather than our freeform way of listing response codes in our
api-ref, we should be using the os-api-ref extension option to
get nicely formatted response code listings.

https://docs.openstack.org/os-api-ref/latest/usage.html#rest-status-code

Change-Id: Iee21f54fe7cf0ea28258966e2d0f8fa2849c83f2
2018-03-08 21:59:37 -06:00

55 lines
719 B
ReStructuredText

.. -*- rst -*-
API extensions (extensions)
===========================
List API extensions
~~~~~~~~~~~~~~~~~~~
.. rest_method:: GET /v2/{project_id}/extensions
Lists Block Storage API extensions.
Response codes
~~~~~~~~~~~~~~
.. rest_status_code:: success ../status.yaml
- 200
Request
-------
.. rest_parameters:: parameters.yaml
- project_id: project_id_path
Response Parameters
-------------------
.. rest_parameters:: parameters.yaml
- updated: updated
- description: description
- links: links
- namespace: namespace
- alias: alias
- name: name
Response Example
----------------
.. literalinclude:: ./samples/extensions-list-response.json
:language: javascript