From a0b85d6f0611d98e21d2d05ade8290f14327f17a Mon Sep 17 00:00:00 2001 From: Ianeta Hutchinson Date: Wed, 28 Sep 2016 14:13:51 -0500 Subject: [PATCH] Fixes RST markup error to create a code-box. Change-Id: Ief06eaa630befb3d9a45ad9177cc40d5ccdf6f34 Closes-Bug: #1628643 --- doc/source/policy_enforcement.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/source/policy_enforcement.rst b/doc/source/policy_enforcement.rst index c0a26dfba027..23699f4ddd16 100644 --- a/doc/source/policy_enforcement.rst +++ b/doc/source/policy_enforcement.rst @@ -134,9 +134,8 @@ After group the policy rules for different API, we can separate them into different files. Then deployer will more clear for which rule he can set for specific API. The rules can be grouped as below: - * policy.json: It only contains the generic rule, like: + * policy.json: It only contains the generic rule, like: :: -:: "context_is_admin": "role:admin", "admin_or_owner": "is_admin:True or project_id:%(project_id)s", "default": "rule:admin_or_owner",