fix(cli): add feature flag to control subscription field redaction behavior #13827
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
sobolk
approved these changes
Jun 19, 2024
awsluja
approved these changes
Jun 19, 2024
dpilch
approved these changes
Jun 19, 2024
|
2 questions here:
|
2 tasks
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.
Add a new FF for data plugin to allow customers to opt-in for a subscriptions field redaction behavior.
false), relational fields will be over-redacted in mutations response and subscribed clients won't receive this data in payload.true), subscriptions will inherit the auth rules of the model for the relational fields. It means that the relational fields won't be over-redacted on mutations.