Should a replace with only CLI origin replace OpenConfig configuration?
Per gnmi-union_replace.md , When performing a gNMI SetRequest replace operation, the entire configuration that the CLI manages (subject to the namespace rules) should be ‘erased’ and replaced with the contents of the CLI ASCII blob value. It is acknowledged that the entire CLI configuration may contain configuration items which overlap with other origins
Is the expectation that a replace with only CLI origin will replace any OpenConfig configuration that is writeable by CLI?
For a union_replace with only CLI origin, is the expectation that the origin OpenConfig configuration is untouched?
Should a replace with only CLI origin replace OpenConfig configuration?
Per gnmi-union_replace.md ,
When performing a gNMI SetRequest replace operation, the entire configuration that the CLI manages (subject to the namespace rules) should be ‘erased’ and replaced with the contents of the CLI ASCII blob value. It is acknowledged that the entire CLI configuration may contain configuration items which overlap with other originsIs the expectation that a replace with only CLI origin will replace any OpenConfig configuration that is writeable by CLI?
For a union_replace with only CLI origin, is the expectation that the origin OpenConfig configuration is untouched?