Typo in description (Additionnally -> Additionally). And since we have to make the fix we can enrich a little bit the API description.
Errors 404 and 409 didn't have the status in the response
Error 500 wasn't pointing to the components/schema so it had a wrong format
Error 400 in GET and DELETE /subscriptions/{subscription_id} had INVALID_INPUT instead of INVALID_ARGUMENT -> aligned with commonalities and moved to componentes/responses so it can be reused.
Path parameter subscriptionId schema was duplicated -> moved to components/parameters so it can be reused
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
A few minor corrections found in the yaml:
Additionnally->Additionally). And since we have to make the fix we can enrich a little bit the API description.Which issue(s) this PR fixes:
Fixes #79