Trifle API support for Trifle key access group #166
Merged
Conversation
This file contains 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
alvinsee
force-pushed
the
gelareh/accessGroup
branch
from
79ed4af
to
233db37
Compare
alvinsee
approved these changes
Sep 29, 2023
|
LGTM |
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.
This PR adds support for access groups to Trifle keys.
AccessGroup specifies the access group the Trifle key belongs to. Specifying this attribute will mean that all key related APIs will be limited to the specified access group (of which the calling application must be a member to obtain matching results.)
It is recommended that this value is set.
If the access group is not set, Trifle keys are created in the application's default access group.