A.5 Complete update of a resource

32.1583GPPDesign rules for REpresentational State Transfer (REST) Solution Sets (SS)Management and orchestrationRelease 17TS

The following example updates a "XyzFunction" resource. Only the "attrA" attribute is updated with a new value "def". The "attrB" attribute is set to the old value "551", but still the "attrB" attribute needs to be present in the resource representation contained in the request message body. Otherwise "attrB" would be deleted due to the replace semantics of HTTP PUT.

PUT /SubNetwork=SN1/ManagedElement=ME1/XyzFunction=XYZF1 HTTP/1.1 Host: example.org Content-Type: application/json { "id": "XYZF1", "attributes": { "attrA": "def", "attrB": 551 } }

When a non leaf resource is updated, contained resources are not included. For example, the following resource representation in the message body updates the "ManagedElement" resource only. It does not delete the contained "XyzFunction" resources.

PUT /SubNetwork=SN1/ManagedElement=ME1 HTTP/1.1 Host: example.org Content-Type: application/json { "id": "ME1", "attributes": { "userLabel": "Berlin New Label", "vendorName": "Company XY", "location": "TV Tower" } }