Check whether 429 and 500 errors are needed for this API

Problem description

429 and 500 are more generic 'API gateway' errors, is there a reason to include them here?

Expected behavior

Check and remove as necessary

Alternative solution

Additional context

@Kevsy

Thanks @Kevsy. Checked against the CAMARA API Design Guide (section 3.2.1, same wording in r4.3 and r4.4):

500: 5xx statuses are "not documented by default" and nothing in this API justifies an exception. Removed in the rc. Implementations may still return 500; the mandatory "Additional CAMARA error responses" text in the description covers that.
429: in the tier that "SHOULD be documented based on the API design", so it is the subproject's call. We keep it, since rate limiting will apply to this API in practice and most CAMARA APIs document it. With the move to Commonalities r4.4 it becomes the minimal TooManyRequests429 catalogue response (TOO_MANY_REQUESTS only, QUOTA_EXCEEDED dropped).

Will close this issue with the r4.4 alignment PR.

Address r1.1 review findings in the API definition and test definitions

Navigation Menu