feat(api): add flexible device resolution with query parameter #4858
Conversation
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
heiytor
force-pushed
the
feat/device-resolve
branch
2 times, most recently
from
304ddd7 to
9f02576
Compare
heiytor
changed the title
heiytor
force-pushed
the
feat/device-resolve
branch
from
9f02576 to
fdd21cf
Compare
otavio
reviewed
May 28, 2025
Implement device resolver functionality that allows fetching devices using attributes beyond the default UID. The new `resolver` endpoint accepts different attribute types while automatically scoping results to the current tenant context for security. Currently supported resolvers: - uid - hostname
heiytor
force-pushed
the
feat/device-resolve
branch
from
fdd21cf to
5c9e226
Compare
otavio
approved these changes
May 31, 2025
otavio
approved these changes
Jun 2, 2025
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.
closes #4857
Implement device resolver functionality that allows fetching devices using attributes beyond the default UID. The new
resolverquery parameter accepts different attribute types while automatically scoping results to the current tenant context for security.Currently supported resolvers: