-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instance-identifier defined in ietf-netconf but not mapped in pyangbind #355
Comments
I will be creating a PR for this. Thanks for all those who review it. |
Very sorry for the delay. I ended up having a lot of work in a few projects. I have written a draft PR. I wanted to ask if I also need to write custom logic to check that the value passed is a valid xpath? Instance identifier sets and gets the xpath itself. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the issue?
instance-identifier not being mapped. #123 was opened to address this issue, but got closed due to inactivity. So opening this issue because I don't know how to reopen that issue.
Elaborate on the issue?
I have created a test yang with instance-identifier defined as per RFC 6020
aeroplane.yang
I use this script to compile this yang to a py module using pyangbind
run_pyang.sh
I run above script and get this error
In #123 @robshakir had asked for a patch with what the value instance-identifier should be mapped to. Whoever is the maintainer now, I can submit a patch taking a look at the netconf-rfc for the right mapping.
What version of pyang and pyangbind do you use?
pyangbind version:
PC version:
The text was updated successfully, but these errors were encountered: