summaryrefslogtreecommitdiffstats
path: root/docs/AAI REST API Documentation/nodesApi.rst
diff options
context:
space:
mode:
authorwr148d <wr148d@att.com>2022-11-09 10:45:38 -0500
committerwr148d <wr148d@att.com>2022-11-09 11:23:32 -0500
commite3dc0167581c0a47bdafdf466c88f0dde554bb65 (patch)
tree1f9d66cc5c5c6034cc01c8fe63389a24dec94291 /docs/AAI REST API Documentation/nodesApi.rst
parent21a59387deedaead37f34d9f6fb1d8d1bc8b738e (diff)
[AAI] Fix doc config files
Issue-ID: AAI-3572 Change-Id: I8785063995fae4c8417e515928c0237bcd935c9f Signed-off-by: wr148d <wr148d@att.com>
Diffstat (limited to 'docs/AAI REST API Documentation/nodesApi.rst')
-rw-r--r--docs/AAI REST API Documentation/nodesApi.rst21
1 files changed, 4 insertions, 17 deletions
diff --git a/docs/AAI REST API Documentation/nodesApi.rst b/docs/AAI REST API Documentation/nodesApi.rst
index e54c0360..14c51c85 100644
--- a/docs/AAI REST API Documentation/nodesApi.rst
+++ b/docs/AAI REST API Documentation/nodesApi.rst
@@ -18,8 +18,6 @@ in querying AAI, allowing clients to circumvent the need to know
every key in the hierarchy. Using the previous example, the below is
how the API called would change for looking up a vserver by name:
-.. code::
-
GET /aai/v$/cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers?vserver-name={vserver-name}
becomes
GET /aai/v$/nodes/vservers?vserver-name={vserver-name}
@@ -35,19 +33,16 @@ API URI
nodes can be used to start a URI from any node type, whether singular or plural.
-.. code::
GET /aai/v$/nodes/{plural}
OR
GET /aai/v$/nodes/{singular}/{key}
From there, it can be expanded on similarly to our Resources API. For example:
-.. code::
-
GET /aai/v$/nodes/{plural}?{property}={value}
-
+
GET /aai/v$/nodes/tenant/{tenant-id}/vservers
-
+
GET /aai/v$/nodes/generic-vnf/{vnf-id}/related-to/platforms
Optional Query Parameters
@@ -64,8 +59,6 @@ returned. By default the output will be depth = 0 (no "children", only
format query parameter, it will only apply to the on the resource or
resource_and_url formats.
-.. code::
-
GET /aai/v$/nodes/{plural}/{singular}/{key}?depth={integer}
Nodes Only
@@ -74,8 +67,6 @@ Nodes Only
You can pass a nodes only query parameter to have the output only contain
the object properties with no relationships.
-.. code::
-
GET /aai/v$/nodes/{plural}/{singular}/{key}?nodes-only
OR
GET /aai/v$/nodes/{plural}/{singular}/{key}?format={format}&nodesOnly=true
@@ -84,12 +75,10 @@ Format
~~~~~~
You can optionally request an output format different from the default
-REST API output. You can reference the list of formats on the `Custom
-Query <customQueries.html>`_ wiki page for the full list of available
+REST API output. You can reference the list of formats on the
+Query wiki page for the full list of available
formats and examples.
-.. code::
-
GET /aai/v$/nodes/{plural}/{singular}/{key}?format={format}
Usage with Custom Query
@@ -99,7 +88,5 @@ The Nodes API can be called directly or as the start node for Custom
Queries. Please reference the Custom Queries wiki page for full
documentation on how to use that interface.
-.. code::
-
PUT /aai/v$/query?format={format} with payload like..
{ "start": ["nodes/{plural}/{singular}/{key}"], "query": "query/{query-name}" }