openstack/cinder
Code Issues Proposed changes

Fix indentation in docs

Browse Source 
cli/cli-manage-volumes.rst
Current indentation is wrongly interpreted as quotation.

Change-Id: I5061fcd2256c24814f0868370d07f8c6dd0ae8e3
This commit is contained in:
David Rabel 2018-08-02 11:44:03 +02:00
parent 8bbbce8964
commit b0e9ee1d50
1 changed files with 26 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/source/cli/cli-manage-volumes.rst
View File

@ -502,19 +502,19 @@ Name or ID of volume to transfer.
``--no-snapshots``
Transfer the volume without snapshots.
The volume must be in an ``available`` state or the request will be
denied. If the transfer request is valid in the database (that is, it
has not expired or been deleted), the volume is placed in an
``awaiting-transfer`` state. For example:
The volume must be in an ``available`` state or the request will be
denied. If the transfer request is valid in the database (that is, it
has not expired or been deleted), the volume is placed in an
``awaiting-transfer`` state. For example:
.. code-block:: console
.. code-block:: console
$ openstack volume transfer request create a1cdace0-08e4-4dc7-b9dc-457e9bcfe25f
The output shows the volume transfer ID in the ``id`` row and the
authorization key.
The output shows the volume transfer ID in the ``id`` row and the
authorization key.
.. code-block:: console
.. code-block:: console
+------------+--------------------------------------+
| Field | Value |
@ -526,12 +526,12 @@ Transfer the volume without snapshots.
| volume_id | a1cdace0-08e4-4dc7-b9dc-457e9bcfe25f |
+------------+--------------------------------------+
.. note::
.. note::
Optionally, you can specify a name for the transfer by using the
``--name transferName`` parameter.
.. note::
.. note::
While the ``auth_key`` property is visible in the output of
``openstack volume transfer request create VOLUME_ID``, it will not be