-
Notifications
You must be signed in to change notification settings - Fork 72
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 Privacy Center to the default development build #1262
Conversation
This fixes `nox -s dev -- pc` to run the "built" privacy center via docker compose, which just required mounting a config.json. This is still a bit messy but this will work for both development & production uses. While doing this, I also renamed the config variables for the PC to not reference "fidesops" explicitly, while maintaining backwards compatibility.
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.
Just one small nit with the mock config.json
otherwise it looks great. It like npm run format
needs to be ran to pass the privacy center lint.
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.
Looks good! I think everything is ready barring passing CI
Great, thanks @TheAndrewJackson 👍 |
Closes #1164
Closes #1141
Code Changes
pc
as an optional arg tonox
commands:nox -s dev -- pc
,nox -s build -- pc
server_url_development
andserver_url_production
fidesops_host_development
andfidesops_host_production
Note that I ended up using
git cherry-pick
to grab commits from #1145, which this PR replaces.Steps to Confirm
nox -s dev -- pc
and confirmed that privacy center loaded at http://localhost:3001 (after a long build delay!)nox -s quickstart
and confirmed that the privacy center can be used to submit a request for [email protected] (once Step Three has completed)Pre-Merge Checklist
CHANGELOG.md
Description Of Changes
This makes the privacy center a "first-class" service in the build, whereas historically it's only been developed with using
npm
commands in the sub-directory. It's still a bit slow to build and could use additional TLC, but this is a big improvement.