Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "GOCDB/Write API/Development"

From EGIWiki
Jump to navigation Jump to search
 
(10 intermediate revisions by the same user not shown)
Line 2: Line 2:


== Timeline ==
== Timeline ==
The Alpha release for the write API is planned for the W/C 19th of September. This will allow at least a subset of the initially panned urls to be tested, including authentication.
The Alpha release for the write API is planned for the W/C <strike>19th of September</strike> 24th October. This will allow at least a subset of the initially panned urls to be tested, including authentication.


== Initially supported urls  ==
== Initially supported urls  ==
 
Details of the methods implemented in the write API can be found on [[GOCDB/Write_API/Technical_Documentation#Supported_methods|Technical Documentation page]].
The following table shows the methods and URLs that we plan to implement
 
=== Site methods  ===
 
{| cellspacing="0" cellpadding="7" border="1" class="wikitable"
|-
! scope="col" | '''Method'''
! scope="col" | '''URL'''
! scope="col" | '''Request Body'''
! scope="col" | '''Function'''
|-
| POST
| &lt;apiurl&gt;/v5/Site/&lt;Site ID&gt;/ExtensionProperties
| Key value pairs in JSON Format e.g. ''Note 1''
| Adds the extension properties defined in the request to the Site with the given ID (fails if any of the extension properties are already defined)
|-
| PUT
| &lt;apiurl&gt;/v5/Site/&lt;Site ID&gt;/ExtensionProperties
| Key value pairs in JSON Format e.g. ''Note 1''
| Replaces the extension properties for the site with the given ID with those in the request (If none of them are currently defined, the it is functionally equivalent to POST)
|-
| DELETE
| &lt;apiurl&gt;/v5/Site/&lt;Site ID&gt;/ExtensionProperties
| Key value pairs in JSON Format e.g. ''Note 1''
| Removes all the extension properties specified in the request body for the identified site (fails if any of the listed properties are not currently defined. ''Note: values do not have to be defined, an empty string can be provided instead. If a value is provided, it must be correct. See Note 3 for examples.''
|-
| DELETE
| &lt;apiurl&gt;/v5/Site/&lt;Site ID&gt;/ExtensionProperties
| None or empty
| Removes all the extension properties for the identified site
|-
| POST
| &lt;apiurl&gt;/v5/Site/&lt;Site ID&gt;/ExtensionProperties/&lt;name&gt;
| Value in JSON Format e.g ''Note 2''
| Adds an extension property of the named site with the named name and value in the request (fails if property with that name is already defined)
|-
| PUT
| &lt;apiurl&gt;/v5/Site/&lt;Site ID&gt;/ExtensionProperties/&lt;name&gt;
| Value in JSON Format e.g ''Note 2''
| Updates the extension property of the named site with the named name and value in the request (If none of that name is already defined, then it is functionally equivalent to POST)
|-
| DELETE
| &lt;apiurl&gt;/v5/Site/&lt;Site ID&gt;/ExtensionProperties/&lt;name&gt;
| None or empty
| Removes the named extension property from the named site (fails if request body is present, or the named property is not defined for the identified Site)
|}
 
=== Service methods  ===
 
{| cellspacing="0" cellpadding="7" border="1" class="wikitable"
|-
! scope="col" | '''Method'''
! scope="col" | '''URL'''
! scope="col" | '''Request Body'''
! scope="col" | '''Function'''
|-
| POST
| &lt;apiurl&gt;/v5/Service/&lt;Service ID&gt;/ExtensionProperties
| Key value pairs in JSON Format e.g. ''Note 1''
| Adds the extension properties defined in the request to the service with the given ID (fails if any of the extension properties are already defined)
|-
| PUT
| &lt;apiurl&gt;/v5/Service/&lt;Service ID&gt;/ExtensionProperties
| Key value pairs in JSON Format e.g. ''Note 1''
| Replaces the extension properties for the service with the given ID with those in the request (If none of them are currently defined, the it is functionally equivalent to POST)
|-
| DELETE
| &lt;apiurl&gt;/v5/Service/&lt;Service ID&gt;/ExtensionProperties
| Key value pairs in JSON Format e.g. ''Note 1''
| Removes all the extension properties specified in the request body for the identified service (fails if any of the listed properties are not currently defined)
|-
| DELETE
| &lt;apiurl&gt;/v5/Service/&lt;Service ID&gt;/ExtensionProperties
| None or empty
| Removes all the extension properties for the identified service
|-
| POST
| &lt;apiurl&gt;/v5/Service/&lt;Service ID&gt;/ExtensionProperties/&lt;name&gt;
| Value in JSON Format e.g ''Note 2''
| Adds an extension property of the named service with the named name and value in the request (fails if property with that name is already defined)
|-
| PUT
| &lt;apiurl&gt;/v5/Service/&lt;Service ID&gt;/ExtensionProperties/&lt;name&gt;
| Value in JSON Format e.g ''Note 2''
| Updates the extension property of the named service with the named name and value in the request (If none of that name is already defined, then it is functionally equivalent to POST)
|-
| DELETE
| &lt;apiurl&gt;/v5/Service/&lt;Service ID&gt;/ExtensionProperties/&lt;name&gt;
| None or empty
| Removes the named extension property from the named service (fails if request body is present, or the named property is not defined for the identified site)
|}
 
=== Service Endpoint methods  ===
 
{| cellspacing="0" cellpadding="7" border="1" class="wikitable"
|-
! scope="col" | '''Method'''
! scope="col" | '''URL'''
! scope="col" | '''Request Body'''
! scope="col" | '''Function'''
|-
| POST
| &lt;apiurl&gt;/v5/EndPoint/&lt;End point ID&gt;/ExtensionProperties
| Key value pairs in JSON Format e.g. ''Note 1''
| Adds the extension properties defined in the request to the SE with the given ID&nbsp; (fails if any of the extension properties are already defined)
|-
| PUT
| &lt;apiurl&gt;/v5/EndPoint/&lt;End point ID&gt;/ExtensionProperties
| Key value pairs in JSON Format e.g. ''Note 1''
| Replaces the extension properties for the SE with the given ID with those in the request (If none of them are currently defined, the it is functionally equivalent to POST)
|-
| DELETE
| &lt;apiurl&gt;/v5/EndPoint/&lt;End point ID&gt;/ExtensionProperties
| Key value pairs in JSON Format e.g. ''Note 1''
| Removes all the extension properties specified in the request body for the identified SE (fails if any of the listed properties are not currently defined)<br>
|-
| DELETE
| &lt;apiurl&gt;/v5/EndPoint/&lt;End point ID&gt;/ExtensionProperties
| None or empty<br>
| Removes all the extension properties for the identified SE
|-
| POST
| &lt;apiurl&gt;/v5/EndPoint/&lt;End point ID&gt;/ExtensionProperties/&lt;name&gt;
| Value in JSON Format e.g ''Note 2''<br>
| Adds an extension property of the named SE with the named name and value in the request (fails if property with that name is already defined)
|-
| PUT
| &lt;apiurl&gt;/v5/EndPoint/&lt;End point ID&gt;/ExtensionProperties/&lt;name&gt;
| Value in JSON Format e.g ''Note 2''
| Updates the extension property of the named SE with the named name and value in the request (If none of that name is already defined, then it is functionally equivalent to POST)
|-
| DELETE
| &lt;apiurl&gt;/v5/EndPoint/&lt;End point ID&gt;/ExtensionProperties/&lt;name&gt;
| None or empty
| Removes the named extension property from the named SE (fails if request body is present, or the named property is not defined for the identified SE)
|}
 
''Note 1:'' [{"PROPERTY1NAME":"PROPERTY1VALUE","PROPERTY2NAME":"PROPERTY2VALUE","PROPERTY3NAME":"PROPERTY3VALUE"}]  
 
''Note 2:'' [{"value":"PROPERTYVALUE"}]


== Proposed authorisation mechanism ==
== Proposed authorisation mechanism ==

Latest revision as of 14:37, 25 October 2016

Write API Development

Timeline

The Alpha release for the write API is planned for the W/C 19th of September 24th October. This will allow at least a subset of the initially panned urls to be tested, including authentication.

Initially supported urls

Details of the methods implemented in the write API can be found on Technical Documentation page.

Proposed authorisation mechanism

The proposed method for authentication for the write API is initially by X509 certificate. Each site will be able to define a list of authorised robot DNs that may make changes through the write API. The same authentication mechanism will be used as for the rest of GOCDB.

Github

The current working branch for this work can be found here.