Support device access states and state notifications#91
Open
hubertp-ericsson wants to merge 6 commits intocamaraproject:mainfrom
Open
Support device access states and state notifications#91hubertp-ericsson wants to merge 6 commits intocamaraproject:mainfrom
hubertp-ericsson wants to merge 6 commits intocamaraproject:mainfrom
Conversation
hubertp-ericsson
requested review from
PeterKovacs2,
carlosromerog,
eric-murray and
tlohmar
as code owners
SteveV-Vodafone
approved these changes
Feb 6, 2026
Contributor
Author
|
Here is the slide I showed in today's call. |
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
3 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:
This PR proposes to support asynchronous device access creation and device access lifecycle. It introduces a very simple state machine which captures the basic states of the device access of interest to the API consumer, namely: REQUESTED, GRANTED, and DENIED. Upon a POST request to create a device access the access enters into the REQUESTED state and a 201 response is returned. After that the device access will transition to GRANTED and/or DENIED depending on the results of backend operations. The state information is stored in the access resource, while state changes are notified (if requested) using the standard Camara notification mechanism.
Which issue(s) this PR fixes:
Fixes #40
Special notes for reviewers:
Changelog input
Additional documentation
This section can be blank.