gNMI Get and Set support
More...
gNMI Get and Set support
◆ get_first_edit_entry()
Get the first edit entry in editsQ.
- Parameters
-
cb | gnmi edits control block |
- Returns
- pointer to the first entry or NULL if empty Q
◆ get_next_edit_entry()
Get the next edit entry in the editsQ.
- Parameters
-
- Returns
- pointer to the next entry or NULL
◆ ypgnmi_check_edits_status()
Check if any of the requested edits failed.
If so, need to set all other successfull or not completed edits to aborted status
- Parameters
-
ecb | edit control block to use |
- Returns
- TRUE if any edit had an error
◆ ypgnmi_free_ecb()
◆ ypgnmi_free_edit()
Free a yp-gnmi Edit entries.
- Parameters
-
◆ ypgnmi_free_gcb()
◆ ypgnmi_new_ecb()
◆ ypgnmi_new_edit()
Create a new yp-gnmi Edit entriy.
- Parameters
-
path_str | specified path for the edit |
input | input if not DELETE op |
editop | edit operation |
- Returns
- pointer to initialized edit entry, or NULL if malloc error
◆ ypgnmi_new_gcb()
◆ ypgnmi_set_edit_status()
void ypgnmi_set_edit_status |
( |
rpc_msg_t * |
msg, |
|
|
const xmlChar * |
edit_id, |
|
|
status_t |
res |
|
) |
| |
Set the error status to the gNMI edit.
To be used in the return message.
In the case that any operation within the SetRequest message fails, then (as per Section 3.4.3), the target MUST NOT apply any of the specified changes, and MUST consider the transaction as failed. The target SHOULD set the status code of the SetResponse message to Aborted (10), along with an appropriate error message, and MUST set the message field of the UpdateResult corresponding to the failed operation to an Error message indicating failure. In the case that the processed operation is not the only operation within the SetRequest the target MUST set the message field of the UpdateResult messages for all other operations, setting the code field to Aborted (10).
- Parameters
-
msg | current msg header containing the ECB |
edit_id | edit to update the status |
res | status to set |