...
| Expand | |
|---|---|
|
...
| Expand | |
|---|---|
|
...
| Expand | |
|---|---|
|
...
| Expand | |
|---|---|
Walking back through relationships in the simple format:Let's say you got back a large tree of output in the simple format and need to go through the list of objects to understand their relationships. For example, the output returned vnfs, vservers, pservers and complexes but you want to only look at the results of a particular complex. First, we'll find the JSON object for the complex by looking at the result objects for one with "node-type": "complex" and "physical-location-id": (the CLLI of the location you want to filter on) within the "properties" object. Next you would check the "related-to" object array for objects with "node-type": "pserver", take the "id"s and search for objects with those IDs in the results object array. You can keep crawling through the results in this way until you reach the objects you need. You can use this method for any property you want to filter on.
|
...
Symbol | Examples | Description |
|---|---|---|
| [] | [node1, node2] | Used for creating a union between nodes. |
| () | node('property','filter') node(> node-filter) | Used for filtering the current node. Can be used with properties or filtering by related nodes, and multiple filters can be applied at once. |
| * | node* node*('property','filter') | Used to return the current node, assuming it meets any filters. |
| > | node1 > node2 | Used to traverse between nodes |
...