Interface: NmdaOps
Defined in: netconf/src/operations/nmda.ts:101
What client.ops.nmda holds.
Methods
editData()
editData(options): Promise<RpcReply>;Defined in: netconf/src/operations/nmda.ts:119
<edit-data>: always rollback-on-error. A JSON config is converted with the datastore's YANG schema, as for editConfig.
Parameters
options
Returns
Promise<RpcReply>
getData()
Call Signature
getData(options): Promise<YangJsonObject>;Defined in: netconf/src/operations/nmda.ts:110
<get-data>: resolves with the reply's <data> element, or with format: 'json', an RFC 7951 JSON object typed by the server's YANG schema for the datastore. withOrigin origins become RFC 7952 ietf-origin:origin annotations. format and json are never sent.
Parameters
options
GetDataOptions & RpcOptions & JsonFormat
Returns
Promise<YangJsonObject>
Throws
SchemaUnavailableError or a YANG data error with format: 'json' and json.requireSchema, when the data can't be typed.
Call Signature
getData(options): Promise<XmlElement>;Defined in: netconf/src/operations/nmda.ts:112
<get-data>: resolves with the reply's <data> element.
Parameters
options
GetDataOptions & RpcOptions & XmlFormat
Returns
Promise<XmlElement>
Call Signature
getData(options): Promise<
| XmlElement
| YangJsonObject>;Defined in: netconf/src/operations/nmda.ts:114
<get-data>: resolves with <data>, or RFC 7951 JSON with format: 'json'.
Parameters
options
GetDataOptions & RpcOptions & FormatOptions
Returns
Promise< | XmlElement | YangJsonObject>