openstack/cinder
Code Issues Proposed changes

cinder:api-ref replace mention of "policy.json"

Browse Source 
As end user can use either of "policy.json" or "policy.yaml" , so need
replace the mentioning of "policy.json" to the just "policy
configuration file" in api-ref.

Change-Id: Ibb8f56a89d3f188be18cc4ee7de493910a02fb98
Closes-Bug: #1875643
This commit is contained in:
vinay_m 2020-07-07 20:55:09 +05:30
parent a323a026f4
commit 780a23b4a2
4 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
api-ref/source/v2/consistencygroups-v2.inc
View File

@ -10,7 +10,7 @@ restore this database from a previous point in time, it makes sense
to restore the logs, tables, and configuration together from the
exact same point in time.
Use the ``policy.json`` file to grant permissions for these actions
Use the policy configuration file to grant permissions for these actions
to limit roles.

6
api-ref/source/v2/volumes-v2-volumes-actions.inc
View File

@ -355,7 +355,7 @@ the volume.
Policy defaults enable only users with the administrative role to
perform this operation. Cloud providers can change these permissions
through the ``volume_extension:volume_admin_actions:force_detach`` rule in
the ``policy.json`` file.
the policy configuration file.
Response codes
@ -403,7 +403,7 @@ more than one active read/write attachment.
Policy defaults enable only users with the administrative role or the owner of
the volume to perform this operation. Cloud providers can change these
permissions through the policy.json file.
permissions through the policy configuration file.
Response codes
--------------
@ -445,7 +445,7 @@ that volume has more than one active read/write attachment.
Policy defaults enable only users with the administrative role to perform this
operation. Cloud providers can change these permissions through the
policy.json file.
policy configuration file.
**Preconditions**

2
api-ref/source/v3/consistencygroups-v3.inc
View File

@ -10,7 +10,7 @@ restore this database from a previous point in time, it makes sense
to restore the logs, tables, and configuration together from the
exact same point in time.
Use the ``policy.json`` file to grant permissions for these actions
Use the policy configuration file to grant permissions for these actions
to limit roles.

6
api-ref/source/v3/volumes-v3-volumes-actions.inc
View File

@ -413,7 +413,7 @@ the volume.
Policy defaults enable only users with the administrative role to
perform this operation. Cloud providers can change these permissions
through the ``volume_extension:volume_admin_actions:force_detach`` rule in
the ``policy.json`` file.
the policy configuration file.
Response codes
--------------
@ -459,7 +459,7 @@ more than one active read/write attachment.
Policy defaults enable only users with the administrative role or the owner of
the volume to perform this operation. Cloud providers can change these
permissions through the policy.json file.
permissions through the policy configuration file.
Response codes
--------------
@ -502,7 +502,7 @@ that volume has more than one active read/write attachment.
Policy defaults enable only users with the administrative role to perform this
operation. Cloud providers can change these permissions through the
policy.json file.
policy configuration file.
.. _3.16 microversion: https://docs.openstack.org/cinder/latest/contributor/api_microversion_history.html#id15