CAMARA_Common.yaml aligment with multiple device identifiers logic#570
Merged
rartych merged 2 commits intocamaraproject:mainfrom Jan 14, 2026
Conversation
PedroDiez
requested review from
jlurien,
patrice-conil,
rartych and
shilpa-padgaonkar
as code owners
rartych
reviewed
Dec 17, 2025
Co-authored-by: Rafal Artych <[email protected]>
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
4 participants
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:
In MetaRelease Fall25, IDENTIFIER_MISMATCH exception is removed. In other words, when an API Client indicates more than one identifier for a device, API provider will take one of them for the API logic, without performing any matching checking among identifiers provided by API client.
Reference:
#431
In CAMARA_Common.yaml it is reflected for device object:
NOTE1: the network operator might support only a subset of these options. The API invoker can provide multiple identifiers to be compatible across different network operators. In this case the identifiers MUST belong to the same device.
And this is misleading, because now the API logic does not perform any matching among them so as it is not an issue nor a requirement that they MUST belong to the same device.
Which issue(s) this PR fixes:
Fixes #566
Does this PR introduce a breaking change?
Special notes for reviewers:
Changelog input
Additional documentation
This section can be blank.