From 70fe12250513502b940cdb1f7536927617e8f2d7 Mon Sep 17 00:00:00 2001 From: PEDRO DIEZ GARCIA Date: Tue, 3 Dec 2024 22:18:37 +0100 Subject: [PATCH] Error alignments for Event Notifications Artifact --- artifacts/notification-as-cloud-event.yaml | 4 ---- documentation/API-design-guidelines.md | 2 +- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/artifacts/notification-as-cloud-event.yaml b/artifacts/notification-as-cloud-event.yaml index 5ed26967..02906cc5 100644 --- a/artifacts/notification-as-cloud-event.yaml +++ b/artifacts/notification-as-cloud-event.yaml @@ -101,10 +101,6 @@ paths: $ref: "#/components/responses/Generic410" 429: $ref: "#/components/responses/Generic429" - 500: - $ref: "#/components/responses/Generic500" - 503: - $ref: "#/components/responses/Generic503" components: securitySchemes: notificationsBearerAuth: diff --git a/documentation/API-design-guidelines.md b/documentation/API-design-guidelines.md index 4ac2f663..7f67515d 100644 --- a/documentation/API-design-guidelines.md +++ b/documentation/API-design-guidelines.md @@ -1965,7 +1965,7 @@ Note: The "subscription-ends" notification is not counted in the `subscriptionMa Error definitions are described in this guideline applies for event notification. The Following Error codes must be present: -* for `POST`: 400, 401, 403, 500, 503 +* for `POST`: 400, 401, 403, 410, 429 #### Correlation Management To manage correlation between the subscription management and the event notification (as these are two distinct operations):