From 780a23b4a2fb1290b7e8f76c99663b99fed54add Mon Sep 17 00:00:00 2001 From: vinay_m Date: Tue, 7 Jul 2020 20:55:09 +0530 Subject: [PATCH] cinder:api-ref replace mention of "policy.json" 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 --- api-ref/source/v2/consistencygroups-v2.inc | 2 +- api-ref/source/v2/volumes-v2-volumes-actions.inc | 6 +++--- api-ref/source/v3/consistencygroups-v3.inc | 2 +- api-ref/source/v3/volumes-v3-volumes-actions.inc | 6 +++--- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/api-ref/source/v2/consistencygroups-v2.inc b/api-ref/source/v2/consistencygroups-v2.inc index fa90e96a12e..8a0935c4f68 100644 --- a/api-ref/source/v2/consistencygroups-v2.inc +++ b/api-ref/source/v2/consistencygroups-v2.inc @@ -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. diff --git a/api-ref/source/v2/volumes-v2-volumes-actions.inc b/api-ref/source/v2/volumes-v2-volumes-actions.inc index 94830543919..691d4436bba 100644 --- a/api-ref/source/v2/volumes-v2-volumes-actions.inc +++ b/api-ref/source/v2/volumes-v2-volumes-actions.inc @@ -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** diff --git a/api-ref/source/v3/consistencygroups-v3.inc b/api-ref/source/v3/consistencygroups-v3.inc index 737ab5b6d9f..799491fdd4b 100644 --- a/api-ref/source/v3/consistencygroups-v3.inc +++ b/api-ref/source/v3/consistencygroups-v3.inc @@ -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. diff --git a/api-ref/source/v3/volumes-v3-volumes-actions.inc b/api-ref/source/v3/volumes-v3-volumes-actions.inc index 36774e318cc..009b1c05156 100644 --- a/api-ref/source/v3/volumes-v3-volumes-actions.inc +++ b/api-ref/source/v3/volumes-v3-volumes-actions.inc @@ -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