clean up some sphinx warnings

[dcaegen2.git] / docs / sections / services / slice-analysis-ms / runtime_configuration.rst

diff --git a/docs/sections/services/slice-analysis-ms/runtime_configuration.rst b/docs/sections/services/slice-analysis-ms/runtime_configuration.rst
index a0772c8..26d116d 100644 (file)
--- a/docs/sections/services/slice-analysis-ms/runtime_configuration.rst
+++ b/docs/sections/services/slice-analysis-ms/runtime_configuration.rst
@@ -27,7 +27,7 @@ Deployment
 \r
      1. Enable dcae-slice-analysis-ms in values.yaml. When using the helm chart of OOM to pull up the whole onap environment, dcae-slice-analysis-ms will be automatically installed.\r
 \r
-            .. code-block:: bash\r
+            .. code-block:: yaml\r
 \r
                dcae-slice-analysis-ms:\r
                  enabled: true\r
@@ -37,7 +37,7 @@ Deployment
 \r
      1. Uncomment the following lines. "duration" is the interval of a thread in policy sync container to retrieve latest policy from XCAML PDP engine. The unit of "duration" is seconds.\r
 \r
-             .. code-block:: bash\r
+             .. code-block:: yaml\r
 \r
                 dcaePolicySyncImage: onap/org.onap.dcaegen2.deployments.dcae-services-policy-sync:1.0.1\r
                 policies:\r
@@ -76,7 +76,7 @@ Steps to Use Runtime Configuration
 \r
     request body: policy_type.json\r
 \r
-    .. code-block:: bash\r
+    .. code-block:: json\r
 \r
        {\r
           "tosca_definitions_version": "tosca_simple_yaml_1_1_0",\r
@@ -116,7 +116,7 @@ Steps to Use Runtime Configuration
 \r
     request body: slicems_config_policy.json\r
 \r
-    .. code-block:: bash\r
+    .. code-block:: json\r
 \r
         {\r
           "tosca_definitions_version": "tosca_simple_yaml_1_1_0",\r
@@ -143,24 +143,25 @@ Steps to Use Runtime Configuration
         }\r
 \r
 3. Deploy the policy\r
+\r
     command\r
 \r
     .. code-block:: bash\r
 \r
-    curl -w %{http_code} --silent -k --user 'username:password' -X POST "https://policyPAPApi:6969/policy/pap/v1/pdps/policies" -H "Accept: application/json" -H "Content-Type: application/json" -d @push.json\r
+       curl -w %{http_code} --silent -k --user 'username:password' -X POST "https://policyPAPApi:6969/policy/pap/v1/pdps/policies" -H "Accept: application/json" -H "Content-Type: application/json" -d @push.json\r
 \r
     request body: push.json\r
 \r
-    .. code-block:: bash\r
+    .. code-block:: json\r
 \r
-    {\r
-      "policies": [\r
-        {\r
-          "policy-id": "onap.dcae.slicems.config",\r
-           "policy-version": 1\r
-        }\r
-      ]\r
-    }\r
+       {\r
+         "policies": [\r
+           {\r
+             "policy-id": "onap.dcae.slicems.config",\r
+              "policy-version": 1\r
+           }\r
+         ]\r
+       }\r
 \r
 4. Verify in SliceMS that configurations received\r
 \r
@@ -168,8 +169,8 @@ Steps to Use Runtime Configuration
 \r
 How to Develop Your Own Runtime Configuration\r
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r
+\r
 1. Create your own policy type\r
 2. Create a policy based on your policy type\r
 3. Deploy the policy\r
 4. Verify in SliceMS that configurations received. (Needs to write code in SliceMS to deal with your configurations in advance.)\r
-\r