opengeospatial / opengeospatial/ogcapi-processes
Part 4: Make PATCH /jobs/:id optional
Nobody has claimed this yet.
- Dominant language
- AsciiDoc
- Stars
- 63
- Forks
- 46
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
In openEO the PATCH operation is optional. Many implementations struggle a bit with implementing updating jobs, especially when already executed. I think I'd recommend to not require this endpoint and make it optional. Could be explored again via a link in GET /jobs/:id (we don't have that link defined in openEO yet, but happy to add).
Originally posted by @m-mohr in https://github.com/opengeospatial/ogcapi-processes/pull/437#discussion_r1789880704
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the specification text that defines PATCH /jobs/:id and the GET /jobs/:id links. Confirm how optional operations and links are represented elsewhere, then update the requirement so PATCH is optional and record the intended GET link behavior; done means the affected specification text is consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100