feat: api keys on viewer node #4486
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
dosubot
bot
added
the
size:M
mikeldking
requested changes
Sep 4, 2024
dosubot
bot
added
size:S
mikeldking
approved these changes
Sep 4, 2024
anticorrelator
force-pushed
the
dustin/api-keys-on-viewer-node
branch
from
2e3782e
to
536635f
Compare
anticorrelator
force-pushed
the
dustin/api-keys-on-viewer-node
branch
from
536635f
to
dfb3431
Compare
This was referenced Sep 4, 2024
RogerHYang
pushed a commit
that referenced
this pull request
Sep 21, 2024
* Add API keys to viewer node * Implement api_keys as a resolver on the user node
This was referenced Sep 25, 2024
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.
resolves #4452
Adds an optional
api_keysfield to theUsernode. Theviewernode will populate these API keys on the user if any exist.