Skip to content
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

Open
wants to merge 501 commits into
base: master
Choose a base branch
from
Open

Model-based replace operation using PUT #152

wants to merge 501 commits into from

Conversation

kwangsuk
Copy link
Collaborator

@kwangsuk kwangsuk commented Sep 8, 2022

No description provided.

sachinholla and others added 30 commits April 9, 2020 17:58
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
FRR-BGP Extended Unified Management Framework
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
vidyac86 and others added 17 commits May 6, 2022 07:54
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]>
* 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.
Copy link
Collaborator

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

Copy link
Collaborator Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.