Skip to content

Correcting status code 409 related error information.#569

Merged
rartych merged 7 commits intocamaraproject:mainfrom
tlohmar:DuplicationOfErrorCodeSemantics
Jan 22, 2026
Merged

Correcting status code 409 related error information.#569
rartych merged 7 commits intocamaraproject:mainfrom
tlohmar:DuplicationOfErrorCodeSemantics

Conversation

@tlohmar
Copy link
Copy Markdown
Contributor

@tlohmar tlohmar commented Dec 16, 2025

What type of PR is this?

  • correction

What this PR does / why we need it:

The PR addresses the recommendations proposed in Issue #562, including the deprecation of the error code CONFLICT.
The PR also improves the description, how these aligned error codes are related to the ErrorInfo Object in the response body.

Which issue(s) this PR fixes:

Fixes #562

Does this PR introduce a breaking change?

  • Yes
  • No

Special notes for reviewers:

Changelog input

The recommendations proposed in Issue #562, including the deprecation of the error code `CONFLICT` are addressed. 
The description, how these aligned error codes are related to the `ErrorInfo` Object in the response body is improved. 

Additional documentation

This section can be blank.

docs

Copy link
Copy Markdown
Contributor

@PedroDiez PedroDiez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some editorial suggestions for alignment.

Look good

Co-authored-by: Rafal Artych <[email protected]>
Co-authored-by: Pedro Díez García <[email protected]>
PedroDiez
PedroDiez previously approved these changes Jan 15, 2026
Copy link
Copy Markdown
Contributor

@PedroDiez PedroDiez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

status: 409
code: ABORTED
message: Concurrency conflict.
message: Resource is being modified by another operation. Please retry.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is 'Please retry' always appropriate? The other operation that is modifying the resource may result in a resource state that means the intended operation is no longer required, or is outdated, or could cause conflict if retried. Maybe better to say 'Please wait, and read the new resource state before retrying (if appropriate)'

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to remember that in Commonalities we give only example of the message that should be modified in API definition as needed.
Suggestions are welcome if this example can be improved.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is just an example. The value of the message parameter is not defined by CAMARA. I assume that this comment is resolved by @rartych feedback.

Copy link
Copy Markdown
Contributor Author

@tlohmar tlohmar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thx

Updating the scope/description of the ABORTED Error Code in both, common.yaml and Design Guide.
Copy link
Copy Markdown
Collaborator

@Kevsy Kevsy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Copy Markdown
Contributor

@patrice-conil patrice-conil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Copy Markdown
Contributor

@PedroDiez PedroDiez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rartych rartych merged commit 72b6720 into camaraproject:main Jan 22, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Duplication of error code semantics, i.e. CONFLICT and ALREADY_EXISTS

5 participants