Browse Source

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

changes/99/700799/6
Zuul 1 week ago
committed by Gerrit Code Review
parent
commit
5e6fd64dfb
4 changed files with 8 additions and 8 deletions
  1. +1
    -1
      api-ref/source/v2/consistencygroups-v2.inc
  2. +3
    -3
      api-ref/source/v2/volumes-v2-volumes-actions.inc
  3. +1
    -1
      api-ref/source/v3/consistencygroups-v3.inc
  4. +3
    -3
      api-ref/source/v3/volumes-v3-volumes-actions.inc

+ 1
- 1
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.




+ 3
- 3
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**



+ 1
- 1
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.




+ 3
- 3
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



Loading…
Cancel
Save