Resolve Sphinx issues with syntax highlighting

A new revision of Sphinx has introduced stricter requirements
in parsing console and json types

Change-Id: I99cb9fb64bc134a2a78e82d95028f744f40634b8
This commit is contained in:
Chris MacNaughton 2019-03-29 08:52:15 +01:00
parent c8d81b2cfd
commit 6a64a48682
3 changed files with 6 additions and 5 deletions

View File

@ -460,8 +460,8 @@ Performing Federation authentication
# curl -X POST \
-H "Content-Type: application/json" \
-d '{"auth":{"identity":{"methods":["saml2"],"saml2":{"id":
"<unscoped_token_id>"}},"scope":{"project":{"domain": {"name":
-d '{"auth":{"identity":{"methods":["saml2"],"saml2":{"id": \
"<unscoped_token_id>"}},"scope":{"project":{"domain": {"name": \
"Default"},"name":"service"}}}}' \
-D - http://localhost:5000/v3/auth/tokens

View File

@ -51,6 +51,5 @@ or ``admin``.
"identity:update_endpoint": "rule:cloud_admin",
"identity:delete_endpoint": "rule:cloud_admin",
...
}

View File

@ -294,8 +294,10 @@ following lines to the nova ``policy.json`` file:
.. code:: json
"compute_extension:admin_actions:migrate": "!",
"compute_extension:admin_actions:migrateLive": "!",
{
"compute_extension:admin_actions:migrate": "!",
"compute_extension:admin_actions:migrateLive": "!",
}
Migration network
-----------------