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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add account/ host GDPR enabled flags & account per request type GDPR enabled flags #1564
Add account/ host GDPR enabled flags & account per request type GDPR enabled flags #1564
Changes from 7 commits
e892e3b
2e5df5a
cc7153b
62a62b1
2f1492a
8ff8bc9
10786f6
6297b88
415238c
4215369
f02f0b3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel this additional setting has potential for ambiguous situations. For example, [enabled=true, all others=false], or [enabled=false, all others=true]. With account defaults layered in, activation of the individual settings is even less clear.
What are your thoughts on removing this fallback altogether ? We do not lose any configurability as the behavior can be fully specified by the four settings in the same section, and overrides apply straight on each field.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hhhjort @SyntaxNode My take was that the committee already agreed on the configuration settings so it would be preferred to follow that, though I understand the two versions sometimes deviate from one another. I recognize that potential ambiguity @laurb9 pointed out. How do you guys feel about this?
Regarding account defaults, I figured the defaults for all of these is
nil
; you either need to explicitly set these on the account or fall back to whatever the host settings are.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed that those cases are ambiguous. The intent is to provide an easy on/off switch with the ability to fine tune it if needed per request type. I suppose this is geared toward expressiveness in config. If an account doesn't care about each integration type, it's easier to set one enabled flag instead of four. The fallback also better defines future compatibility if a new integration type is added in the future.
Since this is implementing an already approved spec, I recommend moving this conversation to #1323.
I'd prefer to keep the same settings as PBS-Java currently for simplicity's sake.