Question

You are writing a Python script that uses the requests library and RESTCONF (RFC 8040) to update the description on a set of interfaces across many IOS-XE devices. Multiple automation jobs may run concurrently, and your team requires that an update must fail rather than silently overwrite a change made by another job since your script last read the resource. Which approach correctly implements this safeguard using standard RESTCONF/HTTP mechanisms?

Accepted Answer

Perform a GET on the interface resource, capture the ETag from the response, then send the PATCH with an If-Match header set to that ETag value.

Answer

Send the PATCH with a Content-Type of application/yang-data+json and rely on RESTCONF's default optimistic locking, which is always enabled server-side.

Answer

Add a custom X-Lock-Resource header to the PATCH request so the server queues concurrent writes until the current one completes.

Answer

Wrap the GET and PATCH in a Python threading.Lock() so that only one thread can modify the device at a time.