I'm not familiar with this specific API spec, but I can say that in general the Open APIs that I have come across do not have PUT in their swagger files.
My personal opinion is that there is little to no value in PUT, since you can achieve the same effect by using PATCH.
But I will raise the issue with the Open API leadership so that we can reach a consistent approach across the API model.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------
Original Message:
Sent: Nov 16, 2018 10:15
From: Luís Prates
Subject: TMF639 Resource Inventory Management API Rest Spec V17.0.1
Hi,
Regarding this API I notice that in <g class="gr_ gr_288 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" id="288" data-gr-id="288">specification</g> document there is an operation based on a PUT.
For example for the Resource
"...PUT RESOURCE
This Uniform Contract operation is used to completely replace a RESOUR
Description :
• Used to replace one RESOURCE with another.
Behaviour:
• Returns HTTP/1.1 status code 200 if the request was successful ..."
But on the provided swagger there is no operation for this, any reason for that?
Thanks in advance.
------------------------------
Best Regards,
Luís Prates
Celfocus
------------------------------