Remove Config Backwards Compatibility: Host GDPR Options #3153
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
AlexBVolcy
previously approved these changes
Sep 26, 2023
VeronikaSolovei9
previously approved these changes
Sep 27, 2023
AlexBVolcy
approved these changes
Sep 28, 2023
VeronikaSolovei9
approved these changes
Sep 28, 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.
The upcoming 2.0 release will remove backwards compatibility for deprecated host and account configuration options. This PR removes support for the following host options:
gdpr.tcf2.purpose{1-10}.enabledgdpr.tcf2.purpose_one_treatementgdpr.tcf2.special_purpose1Instead, hosts should use the following respectively:
gdpr.tcf2.purpose{1-10}.enforce_purposegdpr.tcf2.purpose_one_treatmentgdpr.tcf2.special_feature1Also, this PR removes string data type support for
gdpr.tcf2.purpose{1-10}.enforce_purpose. This field must now be specified as a bool. Previously, the enforcement algorithm for a given purpose could be specified through this field by setting it to "full", "basic" and "none". This should now be specified usinggdpr.tcf2.purpose{1-10}.enforce_algo.