-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
libyang: upgrade to v3 step 3 -- port sonic-yang-mgmt #21716
base: master
Are you sure you want to change the base?
Conversation
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
@qiluo-msft @ganglyu this is the next PR in the series of libyang3 porting... |
4ba074f
to
cb482c1
Compare
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
cb482c1
to
cf56243
Compare
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
491a041
to
ef2790d
Compare
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
ef2790d
to
5f82fd2
Compare
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
5f82fd2
to
2a4d521
Compare
A few things of note here: * The paths generated by libyang3 no longer have the prefix before each node, so these changes are valid that strip those. See https://netopeer.liberouter.org/doc/libyang/master/html/howto_x_path.html: ``` As for the format of any prefixes, the standardized JSON (RFC 7951) was used. Summarized, xpath follows these conventions: ... * nodes always inherit their module (prefix) from their parent node so whenever a node is from a different module than its parent, it MUST have a prefix * nodes from the same module as their parent MUST NOT have a prefix ... ``` * The schema dependencies have been enhanced to support references within unions so more paths are returned now.
…s set it to LY_LOSTORE by default (LY_LOLOG) is disabled which is what this was intending
ccea46c
to
394e0eb
Compare
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
fb12c4e
to
14dcadd
Compare
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
14dcadd
to
4bafb2b
Compare
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
4bafb2b
to
a329bb4
Compare
/azp run Azure.sonic-buildimage |
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
GCU calls this over and over. We don't want a whole tree reversal each time, cache!
a329bb4
to
df14eb9
Compare
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
ce4f096
to
eb02b43
Compare
/azp run Azure.sonic-buildimage |
Why I did it
libyang3 porting.
Port of sonic-yang-mgmt
NOTE: this PR actually includes (as a squashed commits) PR #21679, #21719. Please review the individual commits (skipping the squashed commit) otherwise this may seem too large/confusing.
Depends PR #21679, #21719
Work item tracking
How I did it
How to verify it
All PRs listed on #21679 must be merged into a local build tree in order to test due to cross-repository dependencies.
It is expected the CI/CD system to FAIL with this PR due to cross dependencies, so do not treat such failures as a reason to not review these changes.
Which release branch to backport (provide reason below if selected)
None
Tested branch (Please provide the tested image version)
master as of 20250212
Description for the changelog
libyang: upgrade to v3 step 2 -- port sonic-yang-mgmt
Link to config_db schema for YANG module changes
N/A
A picture of a cute animal (not mandatory but encouraged)
Signed-off-by: Brad House (@bradh352)