PYGNMI commit replace is not replacing the running config .

[dnaiga]

PYGNMI commit replace is not replacing the running config .

[sai1274]

Hey @dnaiga
When you try to replace at a leaf level. It just updates the leaf value. But when you try to replace at a container level with leaf value then it will replace whole container config, and you will be left with only leaf value.

gnmiclient.set(prefix="openconfig-system://",replace=[("openconfig-system:system/config",{"hostname":"test"})])

The above one just replaces the leaf config

gnmiclient.set(prefix="openconfig-system://",replace=[("openconfig-system:system",{"config":{"hostname":"test",}})])

But the above statement replaces everything at node level to default values and sets the hostname to test

[akarneliuk]

Thanks @sai1274 for examples and explanation.

@dnaiga could you please test and confirm?

[dnaiga]

Hi Sai,

Thanks for your response, Yes the above config works for me . But i want to know more on , how can we replace the container with empty value so the config is removed from testbed.

As of now , though we don't send the any particular container in the json request (eg:openconfig-system:system), expecting the running config should be replaced with sent json request so that particular container (openconfig-system:system) which is not present in the json request is replaced (removed) from testbed.

currently which not happening , json request (openconfig-system:system) still remains on the testbed not removed .

Please let us know if anyway we can achieve it .

Thanks ,
Divya

[sai1274]

Hey @dnaiga
So your saying that
gnmiclient.set(prefix="openconfig-system://",replace=[("openconfig-system:system",{})]) is not replacing the whole configuration right?
If it's not working in ur case instead of replaces you can delete the container config itself
gnmiclient.set(prefix="openconfig-system://",delete=["openconfig-system:system"]) something like this

[AscendedEntity]

@dnaiga gNMI replace operation is not the same as a commit replace operation. gNMI replace only replaces the configuration under the origin you have provided, not the whole running configuration.

[dnaiga]

Thank you Sai and AscendedEntity, got it clarified taht "gNMI replace operation is not the same as a commit replace operation."

Yes able to delete the config via delete operation !!.

Thanks ,
Divya