From b31816bbe73439bab7546e1412981106ab0c4bf8 Mon Sep 17 00:00:00 2001 From: Jimmy Forsyth Date: Fri, 7 Jun 2019 09:47:07 -0400 Subject: Add instructions for AAF role for sparky Move nodes API block to proper location Issue-ID: AAI-2411 Signed-off-by: Jimmy Forsyth Change-Id: If21e610366c765a251fe4fb78ded7ca90bcfa142 --- docs/AAI REST API Documentation/AAIRESTAPI.rst | 29 +++++++++++----------- .../AAIRESTAPI_DUBLIN.rst | 29 +++++++++++----------- 2 files changed, 30 insertions(+), 28 deletions(-) (limited to 'docs/AAI REST API Documentation') diff --git a/docs/AAI REST API Documentation/AAIRESTAPI.rst b/docs/AAI REST API Documentation/AAIRESTAPI.rst index 5cd758bb..04cd6c08 100644 --- a/docs/AAI REST API Documentation/AAIRESTAPI.rst +++ b/docs/AAI REST API Documentation/AAIRESTAPI.rst @@ -1062,6 +1062,21 @@ The Bulk API allows clients to make multiple requests in a single transaction. Please look for additional details on the following wiki page: `Bulk API `_ +Nodes API +--------- + +In working with A&AI's standard REST API, you may have noticed that +certain API paths have a hierarchy to them and require a client to +know multiple object keys to preform GETs. For example: the vserver +object is under tenant, which is itself under cloud-region. If you +wanted to look up a vserver by name, you would still need to know the +tenant-id and cloud-region-id (and cloud-owner) in order to +successfully perform that GET. The nodes API allows for more freedom +in querying A&AI, allowing clients to circumvent the need to know +every key in the hierarchy. + +See `Nodes API `_ for more information. + AAI Traversal APIs ================== @@ -1082,20 +1097,6 @@ values. Please reference `Nodes Query `_ for details on the API and test queries. -Nodes API ---------- - -In working with A&AI's standard REST API, you may have noticed that -certain API paths have a hierarchy to them and require a client to -know multiple object keys to preform GETs. For example: the vserver -object is under tenant, which is itself under cloud-region. If you -wanted to look up a vserver by name, you would still need to know the -tenant-id and cloud-region-id (and cloud-owner) in order to -successfully perform that GET. The nodes API allows for more freedom -in querying A&AI, allowing clients to circumvent the need to know -every key in the hierarchy. - -See `Nodes API `_ for more information. Generic Queries --------------- diff --git a/docs/AAI REST API Documentation/AAIRESTAPI_DUBLIN.rst b/docs/AAI REST API Documentation/AAIRESTAPI_DUBLIN.rst index 5cd758bb..04cd6c08 100644 --- a/docs/AAI REST API Documentation/AAIRESTAPI_DUBLIN.rst +++ b/docs/AAI REST API Documentation/AAIRESTAPI_DUBLIN.rst @@ -1062,6 +1062,21 @@ The Bulk API allows clients to make multiple requests in a single transaction. Please look for additional details on the following wiki page: `Bulk API `_ +Nodes API +--------- + +In working with A&AI's standard REST API, you may have noticed that +certain API paths have a hierarchy to them and require a client to +know multiple object keys to preform GETs. For example: the vserver +object is under tenant, which is itself under cloud-region. If you +wanted to look up a vserver by name, you would still need to know the +tenant-id and cloud-region-id (and cloud-owner) in order to +successfully perform that GET. The nodes API allows for more freedom +in querying A&AI, allowing clients to circumvent the need to know +every key in the hierarchy. + +See `Nodes API `_ for more information. + AAI Traversal APIs ================== @@ -1082,20 +1097,6 @@ values. Please reference `Nodes Query `_ for details on the API and test queries. -Nodes API ---------- - -In working with A&AI's standard REST API, you may have noticed that -certain API paths have a hierarchy to them and require a client to -know multiple object keys to preform GETs. For example: the vserver -object is under tenant, which is itself under cloud-region. If you -wanted to look up a vserver by name, you would still need to know the -tenant-id and cloud-region-id (and cloud-owner) in order to -successfully perform that GET. The nodes API allows for more freedom -in querying A&AI, allowing clients to circumvent the need to know -every key in the hierarchy. - -See `Nodes API `_ for more information. Generic Queries --------------- -- cgit 1.2.3-korg