apikey: Allow entering a query directly to generate Allowed Fields #3370
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
mastercactapus
changed the title
KatieMSB
previously approved these changes
Oct 24, 2023
KatieMSB
approved these changes
Oct 24, 2023
Forfold
approved these changes
Oct 24, 2023
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.
Description:
Adds the ability to configure Allowed Fields by entering an example query.
Behind the experimental flag
gql-api-keys. Run GoAlert with the command:make start EXPERIMENTAL=gql-api-keysWhich issue(s) this PR fixes:
Part of #3007
Screenshots:
Describe any introduced user-facing changes:
When creating an API key, the multi-select field can be swapped to input an example query directly.