PATCH is a more fine-grained HTTP verb for (partially) updating data via REST. It would be nice to have this option when using the FME Server REST API as it would enable safer and more robust interactions with FME Server data. It may also allow certain organizations to adhere to standards and best practices for developing web applications.
Archived
Implement PATCH for the FME Server REST API
+14- Safer
For anyone interested in having the ability to issue PATCH requests with the FME Server REST API, it would be helpful if you could let us know what endpoints/objects this would be beneficial for.
We have received a request that this would be particularly useful for schedules (i.e. update only some fields for a schedule that already exists in FME Server).
- Contributor
@rylanatsafe For us it would be particulair interested with the following endpoints:
- /repositories/<repository>/items/<item>
- /repositories/<repository>/items/<item>/resources/<resource>
I think with any modification endpoint a specific PATCH endpoint would be beneficial. The current work around is: Get the items -> Existing items can use PUT -> non-existing have to use POST. Which is exactly what a PATCH should encapsulate (existing and non-existing).
