How to generate netconf-confirmed-commit notification #1548
Labels
is:enhancement
Request for adding new feature or enahncing functionality.
status:completed
From the developer perspective, the issue was solved (bug fixed, question answered,...)
Comments
|
Actually, we have completely missed this notification and it is not implemented and never sent. It is not a priority but I have noted it and we will implement it once there is some spare time, will reply here. |
michalvasko
added
the
is:enhancement
|
Hi Michalvasko, |
lePici
added a commit
to lePici/netopeer2
that referenced
this issue
Apr 15, 2024
michalvasko
pushed a commit
that referenced
this issue
Apr 15, 2024
|
Sending |
michalvasko
added
the
status:completed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
sh-5.1# sysrepoctl -h
sysrepoctl - sysrepo YANG schema manipulation tool, compiled with libsysrepo v2.1.84 (SO v7.8.10)
sh-5.1# netopeer2-server -V
netopeer2-server 2.1.36
Use netopeer2-cli to connect server and execute "subscribe" to receive notifications. I modify the candidate data and execute "commit --confirm-timeout 120". I can see the "netconf-config-change", but here is NO "netconf-confirmed-commit ",
After this, I execute command "commit --confirmed-commit", there is still NO "netconf-confirmed-commit "
Am my procedure WRONG? or the "netconf-confirmed-commit" notification is NOT support in the laster code?
The text was updated successfully, but these errors were encountered: