Conversation
…ogue Bumps x-camara-commonalities to 0.9.0, re-copies the additional-error-responses template, and bumps the Design Guide link. Migrates all seven error responses to the r4.4 catalogue: exact matches and the 422 rename keep their declared codes; the 400, 429, and retrieveQosProfiles' 404 narrow to only the codes each operation can return.
…nario Normalizes nine un-prefixed schema pointers to the r4.4 test template's #/ convention, and adds a scenario for retrieveQosProfiles with a name matching no profile, asserting 200 with an empty array.
hdamker
requested review from
benhepworth,
eric-murray and
jlurien
as code owners
September 18, 2026 12:58
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
correction
What this PR does / why we need it:
Brings
qos-profilesinto line with CAMARA Commonalities 0.9.0 (r4.4). A minor-version correction on top of the released1.1.0: three error codes that no path through either operation can produce are removed, everything else is unchanged.Highlights:
x-camara-commonalities: 0.9.0, re-copy the driftedadditional-error-responsesinfo.descriptionblock, and bump the Design Guide link.Generic<status>responses onto the r4.4 catalogue. Four move as exact matches or a pure rename (Unauthenticated401,PermissionDenied403,getQosProfile'sNotFound404, and the local 422 renamed toRetrieveQosProfilesUnprocessable422); three narrow to only the codes the operation can return (BadRequest400,TooManyRequests429, andretrieveQosProfiles' 404 toIdentifierNotFound404).CAMARA_common.yamlexample pool..featuretest-definition OAS pointers to the#/prefix used by the r4.4 test template, and add a scenario forretrieveQosProfileswith anamematching no profile, asserting200with an empty array.Which issue(s) this PR fixes:
Fixes #20
Fixes #21
Special notes for reviewers:
OUT_OF_RANGEon 400,NOT_FOUNDonretrieveQosProfiles's 404,QUOTA_EXCEEDEDon 429) are covered by Narrow qos-profiles error responses to codes each operation can return #21; Align qos-profiles with Commonalities r4.4 #20 covers everything else. Both land together here because Align qos-profiles with Commonalities r4.4 #20 deliberately left those three responses untouched rather than migrating them to a same-code-set catalogue entry first.qos-profiles1.1.0, released inQualityOnDemandr3.2), so each needs a### Removedchangelog entry..featurescenario asserted any of the three removed codes before this change.Changelog input
Additional documentation
This section can be blank.