Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support of 504 Exception in Cloud Events Model #291

Open
PedroDiez opened this issue Aug 30, 2024 · 2 comments · May be fixed by #313
Open

Support of 504 Exception in Cloud Events Model #291

PedroDiez opened this issue Aug 30, 2024 · 2 comments · May be fixed by #313
Assignees
Labels

Comments

@PedroDiez
Copy link
Collaborator

PedroDiez commented Aug 30, 2024

Problem description

Currently in CAMARA CloudEvents Model, Exception 504 (TIMEOUT) is not considered.

It is proposed to consider this exception for Timeout scenario where API Server generates a timeout (e.g. communication failure with BE component).

To be discussed within Commonalities.

Possible evolution

If agreed, to enhance Notifications and Subscription artifacts to incorporate this exception:

Also to check whether some description enhancement is required in section 12 of API Design Guidelines document.

Alternative solution
N/A

Additional context
Background discussion in: #189 (comment)

Issue proposed for MetaRelease Spring 25 - #273

@bigludo7
Copy link
Collaborator

bigludo7 commented Oct 1, 2024

Hello @PedroDiez
Does this point is specific to the subscription or should it be tackled at whole CAMARA level?

I checked some other other API like in device location or QoD and I do not find the 504 while we have it for Carrier billing.

@PedroDiez
Copy link
Collaborator Author

Hi @bigludo7,

Raised the issue for subscription and notification specifically.
Anyway it could be also considered at whole CAMARA level, as the scenario could appear for any API

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants