Changed top-level netconf get-config and get to return <data>..</data> instead of <data><config>...</config></data> to comply to the RFC.
This commit is contained in:
parent
2141b4972a
commit
2d65fdbe93
8 changed files with 89 additions and 40 deletions
48
CHANGELOG.md
48
CHANGELOG.md
|
|
@ -1,13 +1,57 @@
|
|||
# Clixon CHANGELOG
|
||||
|
||||
Major changes:
|
||||
- Changed top-level netconf get-config and get to return <data>..</data> instead of <data><config>...</config></data> to comply to the RFC.
|
||||
-- If you use direct netconf get or get-config calls, you may need to handle the return XML differently.
|
||||
-- RESTCONF and CLI is not affected.
|
||||
-- Example:
|
||||
--- new style: <rpc><get/></rpc> --> <rpc-reply><data><a/></data></rpc-reply>
|
||||
--- old style: <rpc><get/></rpc> --> <rpc-reply><data><config><a/></config></data></rpc-reply>
|
||||
|
||||
|
||||
- Added support for yang presence and no-presence containers. Previous default was "presence".
|
||||
-- This means that empty containers will be removed unless you have used the "presence" yang declaration.
|
||||
-- Example YANG:
|
||||
```
|
||||
container
|
||||
nopresence {
|
||||
leaf j {
|
||||
type string;
|
||||
}
|
||||
}
|
||||
```
|
||||
If you submit "nopresence" without a leaf, it will automatically be removed:
|
||||
```
|
||||
<nopresence/> # removed
|
||||
<nopresence> # not removed
|
||||
<j>hello</j>
|
||||
</nopresence>
|
||||
```
|
||||
|
||||
- Added YANG RPC support for nentconf and CLI. With example rpc documentation and testcase. This replaces the previous "downcall" mechanism.
|
||||
- Added YANG RPC support for netconf and CLI. With example rpc documentation and testcase. This replaces the previous "downcall" mechanism.
|
||||
-- This means you can make netconf rpc calls as defined by YANG.
|
||||
-- However you need to register an RPC backend callback using the backend_rpc_cb_register() function. See documentation and example for more details.
|
||||
-- Note that RESTCONF PUT for RCP calls is not yet supported.
|
||||
-- For example, the following yang rpc definition enables you to run a netconf rpc.
|
||||
```
|
||||
YANG:
|
||||
rpc myrpc {
|
||||
input {
|
||||
leaf name {
|
||||
type string;
|
||||
}
|
||||
}
|
||||
}
|
||||
NETCONF:
|
||||
<rpc><myrpc><name>hello</name><rpc>
|
||||
```
|
||||
|
||||
- Enhanced leafref functionality: (1) validation for leafref forward and backward references; (2)CLI completion for generated cli leafrefs for both absolute and relatve paths.
|
||||
- Enhanced leafref functionality: (1) validation for leafref forward and backward references; (2)CLI completion for generated cli leafrefs for both absolute and relative paths.
|
||||
|
||||
- Added state data: Netconf <get> operation, new backend plugin callback: "plugin_statedata()" for retreiving state data.
|
||||
-- This means that you can use NETCONF <rpc><get/></rpc> and it will return both config and state data.
|
||||
-- It also means that RESTCONF GET will return state data also, if defined.
|
||||
-- However, you need to define state data in a backend callback. See the example and documentation for more details.
|
||||
|
||||
Minor changes:
|
||||
- Removed 'margin' parameter of yang_print().
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue