ianbarrere
commented
5 months ago OK, I see the issue. It appears that when there is a presence container with nothing in it then it doesn't show up in the binding:
container main {
container presence-container {
presence "This is a test container";
}
leaf foo {
type string;
}
}Results in this:
>>> from yang_test import test
>>> test = test()
>>> test.get()
{'main': {'foo': ''}}
>>>But if I add a leaf inside the presence container then it shows up:
container main {
container presence-container {
presence "This is a test container";
leaf bar {
type string;
}
}
leaf foo {
type string;
}
}>>> from yang_test import test
>>> test = test()
>>> test.get()
{'main': {'presence-container': {'bar': ''}, 'foo': ''}}
>>>I personally think it's kind of silly that the IOS-XR unified models, for example, go this route for signaling whether an interface is shutdown or not, but I of course have no power over that decision. Is it possible to extend support in pyangbind for presence containers that have no child elements?
JoseIgnacioTamayo
I came upon this thread from some years ago which indicates that presence containers are now supported in pyangbind, but I can't get my binding to recognize them. The model I'm working with is Cisco-IOS-XR-um-interface-cfg.yang from here. There is a presence container "shutdown" (why they chose to do it that way is beyond me...) which is not showing up as an attribute when I create my binding. Everything else seems to be recognized.
Is there something I need to do to enable presence containers to be created in the binding when I create it?
Relevant versions:
Some output:
Here is the command I used to generate the binding: