This PR aims to define a normalization of error status and code allowed values for CAMARA APIs, by means of the use of a common chema model that can be applied for every excepction scenario.
Taking advantage of this PR also a correction is managed:
422 UNSUPPORTED_DEVICE_IDENTIFIERS exception renamed to 422 UNSUPPORTED_IDENTIFIER indicated in API Design guidelines is also included in CAMARA_common.yaml
Also making exceptions alignment as per this comment in CAMARA_common.yaml. Updates in API Design guidelines Section 6.2 will be managed by #324 and #329
What type of PR is this?
What this PR does / why we need it:
This PR aims to define a normalization of error
status
andcode
allowed values for CAMARA APIs, by means of the use of a common chema model that can be applied for every excepction scenario.Taking advantage of this PR also a correction is managed:
422 UNSUPPORTED_DEVICE_IDENTIFIERS
exception renamed to422 UNSUPPORTED_IDENTIFIER
indicated in API Design guidelines is also included inCAMARA_common.yaml
Also making exceptions alignment as per this comment in
CAMARA_common.yaml
. Updates in API Design guidelines Section 6.2 will be managed by #324 and #329Which issue(s) this PR fixes:
Fixes #196
Does this PR introduce a breaking change?
Special notes for reviewers:
Documentation impacted:
Once this PR is agreed (i.e. the baseline), other artifacts would have to be updated:
We can talk this point in the next commonalities meeting (14/10) and aligned this with @bigludo7
Changelog input
Additional documentation
N/A