-
Notifications
You must be signed in to change notification settings - Fork 33
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
Update location-retrieval for Spring25 #283
Conversation
Align location-retrieval.yaml comm 0.5 for Error
Align error code with comm.0.5
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :)
code: | ||
enum: | ||
- PERMISSION_DENIED | ||
- INVALID_TOKEN_CONTEXT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We may need to remove INVALID_TOKEN_CONTEXT for our APIs. There is an ongoing discussion in Commonalities
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tend to prefer to remove it. What is your view @jlurien as we need probably to move forward with this PR? I remove it, we merge this one and we listen the Commonalities version in case we need to reintroduce it?
fix @location_retrieval_15_device_token_mismatch to use 422 Unnecessary identifier instead of 403 access token mistmatch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@jlurien can we merge it from your side as well with an approve? :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In location-verification PR, I copied from the artifact in Commonalities, the scenarios under
Error scenarios for management of input parameter device
_C01.XX series, and removed the old ones. This way is easier to maintain whatever is changed in the common artifact.
The rest LGTM
@@ -140,7 +140,7 @@ Feature: CAMARA Device location retrieval API, v0.3.0 - Operation retrieveLocati | |||
When the HTTP "POST" request is sent | |||
Then the response status code is 422 | |||
And the response property "$.status" is 422 | |||
And the response property "$.code" is "UNSUPPORTED_DEVICE_IDENTIFIERS" | |||
And the response property "$.code" is "UNSUPPORTED_IDENTIFIERS" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update lines 1 and 15 to vwip
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Updates location-retrieval API with the changes derived from Commonalities and ICM updates
x-camara-guidelines: 0.5.0
Which issue(s) this PR fixes:
Fixes #276, #279
Special notes for reviewers:
There are still some open discussions in Commonalities that may impact this PR, so we will keep it open until there is a final version for x-camara-guidelines: 0.5.0
Changelog input
Additional documentation
This section can be blank.