summaryrefslogtreecommitdiffstats
path: root/docs/api-reference/bp-processor.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/api-reference/bp-processor.rst')
-rw-r--r--docs/api-reference/bp-processor.rst10
1 files changed, 2 insertions, 8 deletions
diff --git a/docs/api-reference/bp-processor.rst b/docs/api-reference/bp-processor.rst
index eb29b093c..efb56b117 100644
--- a/docs/api-reference/bp-processor.rst
+++ b/docs/api-reference/bp-processor.rst
@@ -11,7 +11,7 @@ Introduction
This section shows all resources and endpoints which CDS BP processor currently provides through a swagger file
which is automatically created during CDS build process by Swagger Maven Plugin. A corresponding Postman collection is
also included. Endpoints can also be described using this template
-:download:`api-doc-template.rst <api-doc-template.rst>` but this is not the preferred way to describe the CDS API.
+:download:`api-doc-template.rst <media/api-doc-template.txt>` but this is not the preferred way to describe the CDS API.
You can find a sample workflow tutorial :ref:`below <workflow-tutorial>` which will show how to use the endpoints
in the right order. This will give you a better understanding of the CDS Blueprint Processor API.
@@ -83,9 +83,6 @@ HTTP Status 202 OK
"mappings": {
"dispatcherHandlers": {
"webHandler": [
-
- ...
-
{
"predicate": "{GET /api/v1/blueprint-model, produces [application/json]}",
"handler": "org.onap.ccsdk.cds.blueprintsprocessor.designer.api.BlueprintModelController#allBlueprintModel()",
@@ -144,9 +141,6 @@ HTTP Status 202 OK
}
}
}
-
- ...
-
]
}
},
@@ -247,4 +241,4 @@ Take care that the last step will fail if you don't have a netconf server set up
:width: 500pt
.. |saveResponseImage| image:: media/save-response-postman.png
- :width: 500pt \ No newline at end of file
+ :width: 500pt