-
Notifications
You must be signed in to change notification settings - Fork 73
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
Switch TCF config to env var #4220
Conversation
Passing run #4466 ↗︎
Details:
Review all test suite changes for PR #4220 ↗︎ |
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4220 +/- ##
==========================================
- Coverage 87.67% 87.65% -0.02%
==========================================
Files 333 331 -2
Lines 20743 20695 -48
Branches 2690 2689 -1
==========================================
- Hits 18187 18141 -46
+ Misses 2093 2091 -2
Partials 463 463
☔ View full report in Codecov by Sentry. |
@pattisdr This is currently merging into a larger TCF feature branch. It might be easier to merge this straight into main since there is a migration. If it's low risk to merge it into main I think it'll be worth it. Also, it looks like this PR is failing the performance CI check. Do I need to worry about that for this change? |
@TheAndrewJackson to answer your first question, yes I think this should definitely go into main due to the migration as you point out, can you repoint this branch? |
@pattisdr repointed to main 👍 |
reviewing now thank you 💯 |
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.
Nice changes here @TheAndrewJackson I just want to make sure this works for local development -
docker-compose.yml
Outdated
@@ -28,6 +28,7 @@ services: | |||
FIDES__DEV_MODE: "True" | |||
FIDES__LOGGING__COLORIZE: "True" | |||
FIDES__USER__ANALYTICS_OPT_OUT: "True" | |||
FIDES__CONSENT__TCF_ENABLED: "False" |
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.
It seems like hardcoding this to false is preventing setting tcf_enabled=true in the fides.toml file for local development from taking effect? Can you look at this and verify you can run fides locally with tcf enabled=true set from the fides.toml file? Maybe we can remove this line altogether
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.
Good catch. I'll look into that now
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.
That was causing the issue you described. I removed it from the docker compose file: d99ddb0
I tried updating it to be FIDES__CONSENT__TCF_ENABLED: ${FIDES__CONSENT__TCF_ENABLED-}
but that caused validation issues on startup because it would pass in null instead of a boolean value.
I can't imagine that this change matters much for performance |
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.
Thank you looks good to me!
oooh very excited for this! @TheAndrewJackson can you do me a favor and update this doc with the deetz of the new env var and remove the section about going through |
@allisonking yes! I'll do that now |
Closes #3788
Description Of Changes
This PR rips out the
consent_settings
table and endpoints in favor of using a simpler env var.Code Changes
enable_tcf
fixtureSteps to Confirm
Pre-Merge Checklist
CHANGELOG.md