-
Notifications
You must be signed in to change notification settings - Fork 24
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
Model-based replace operation using PUT #152
base: master
Are you sure you want to change the base?
Conversation
Add REST API versioning details to HLD
* Update Mgmt framework HLD for CLI/Transformer enhancements
respect to OpenAPI 3.0 upgrade
* Update gNMI sections * Address comments
Updated mgmt-framework to include details with
Updated HLD for show ip arp vrf support
Change PortChannel Creation command
Created a new merge request to doc/mgmt
DNS support in SONiC
FRR-BGP Extended Unified Management Framework
EVPN VxLAN HLD
High Level Design Document Rev 0.12
Updating MCLAG Enhancements HLD
Updated with Separate IP klish details
Updated Mclag Enhancements document
remove to udpate latest one
Pruning API support for Query Parameters subtree callbacks (4)
DBAL: Added descriptions of ExistKeysPattern(), GetTablePattern()
And added details about delete notification from SAI and shaper requirements for COPP
Update apps_SONiC_FileSystem_HLD.md
Signed-off-by: tejaswi_goel <[email protected]>
Update Audit_Log_HLD.md
* HAMD RBAC HLD * Added HAM design diagram * Addressed comments
* Add certificate management HLD * Add REST an telemetry CLIs * Update REST and telemetry commands Co-authored-by: Eric Seifert <[email protected]> Co-authored-by: Haemanthi Sree KR <[email protected]> Co-authored-by: Haemanthi Sree <[email protected]>
|
||
### 3.1.1 Changes required by the Transformer Infra | ||
|
||
1) For target ending in list-instance which doesn't exist and is not annotated with subtree, it will be created apart from what is translated from payload(REPLACE).NO DELETE traversal for child yang hierarchy of target since instance never existed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For this case - "list instance creation" if not exist, I hope default value of the leaf nodes also will be created by infra along with the instance creation? Please confirm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. As part of resource creation, a default value will be populated if a YANG node defines it.
Further clarification
No description provided.