yang model table DEVICE_NEIGHBOR_METADATA creation#11894
yang model table DEVICE_NEIGHBOR_METADATA creation#11894jcaiMR merged 3 commits intosonic-net:masterfrom jcaiMR:yang/device_neighbor_metadata
Conversation
|
|
src/sonic-yang-models/yang-models/sonic-device_neighbor_metadata.yang
Outdated
Show resolved
Hide resolved
src/sonic-yang-models/yang-models/sonic-device_neighbor_metadata.yang
Outdated
Show resolved
Hide resolved
|
Unit tests for sonic-config-engine failed. |
|
why do you update submodule for frr? |
|
/easycla |
Thanks for point this out, it's a miss op by commit, I will move it our. |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Latest build failure introduced by https://github.com/sonic-net/sonic-buildimage/pull/ 11848, owner is working on fix. |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
liushilongbuaa
added
Approved for 202205 Branch
and removed
Approved for 202205 Branch
labels
|
@yxieca , the original repo has some issue. Here is the response from github: I have been updated that the affected pull request did not run because the forked repository was duplicated on the 29th of March 2023 and the first one was marked as inactive. The pull request was from the first inactive repository, so the pull request points to a repository ID that doesn't exist, because it somehow was recreated. As you mentioned you won't experience this issue from other forked repositories, but if you have other PRs from the same repository from before March 29, they might run into the same issue. Otherwise other pull requests from the repository should run as expected. |
|
@StormLiangMS , @yxieca , for this PR, auto cherry pick flow didn't work. |
* yang mode support for neighbor metadata * add description in leaf node * modify description
* yang mode support for neighbor metadata * add description in leaf node * modify description Co-authored-by: jcaiMR <[email protected]>
yxieca
added
Approved for 202211 Branch
Cherry Pick Conflict_202211
and removed
Approved for 202205 Branch
labels
7 participants
Why I did it
Add support for DEVICE_NEIGHBOR_METADATA yang model table
How I did it
Create new yang files for DEVICE_NEIGHBOR_METADATA , add UT.
How to verify it
Run UT for sonic-yang-models
Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)
fixes #10545