If it is a list that is accessed, the tailf extension for collections is necessary to wrap the list elements in a root element. This functionality is missing from the RFC 8040.
Supply the following arccept header together with the query
Well, to get to the 'customer' tag you'll need to specify the service instance that you want to get that from.
In your example I'm assuming that "service-id = 114Colt13" is the service instance list key. In this case the curl for the get will look something like this to get the customer tag:
Note that there are some differences between REST API and RESTCONF: * Keys are represented a bit differently in URI:s, instead of '/' use '='. * The module name is required (by default) to prefix first instance in the datastore when namespace changes. * RESTCONF uses the unified datastore by default * RESTCONF queries are "deep" by default, to limit tree depth use the query parameter "depth".
The corresponding RESTCONF URI would be something like
If it is a list that is accessed, the tailf extension for collections is necessary to wrap the list elements in a root element. This functionality is missing from the RFC 8040.
Supply the following arccept header together with the query
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the NSO Developer community:
