Subscriptions and Notifications artifacts errors aligment -enum values- #361
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s for status and code-
PedroDiez
added
enhancement
PedroDiez
requested review from
shilpa-padgaonkar,
rartych,
patrice-conil and
RubenBG7
as code owners
PedroDiez
requested review from
bigludo7,
jlurien,
eric-murray and
fernandopradocabrillo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
This PR is needed in order to align both:
With the Error Model agreed for Metarelease Spring 25, in which for both
statusandcodeenum values are mormative.Which issue(s) this PR fixes:
Fixes #354
Does this PR introduce a breaking change?
Breaking Changes:
event-subscription-template.yamlnew 422 errors are documented (think that makes sense) and also some of them are changed:NOTE: The indication of enum values for
statusandcodemight be understood as a breaking change if a former implementation did not consider in advance and other value was being used.Special notes for reviewers:
notification-as-cloud-event.yaml- Besides Error alignment it is also removed 5xx error references (500 and 503), to be aligned to not document not mandatory errors.Changelog input
Additional documentation
N/A