Closed PedroDiez closed 1 month ago
@PedroDiez and @bigludo7 Do we also want to align this to the PR #194 discussion and get rid of 415 error as well?
I think it is already aligned Shilpa (let's see also Ludovic's view). My understanding:
https://github.com/camaraproject/Commonalities/blob/db4c82976c560fa379cd6e8cc0f391db45569164/artifacts/camara-cloudevents/event-subscription-template.yaml#L51 (415 is removed from notification (callback))
Error "415" is defined/kept for POST /subscriptions (i.e. the case where request body is not in application/json, in this case I assume is being kept due to the input comes from API client and it would be a possible scenario)
@PedroDiez Yes, that's correct, for subscriptions it could still be a possible scenario..
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Align template with #198
Which issue(s) this PR fixes:
Fixes #185 #153
Special notes for reviewers:
Changelog input
Additional documentation
This section can be blank.