Skip to content
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.

Migration to add default access + erasure policies to Fidesops #624

Closed
seanpreston opened this issue Jun 9, 2022 · 0 comments · Fixed by #654
Closed

Migration to add default access + erasure policies to Fidesops #624

seanpreston opened this issue Jun 9, 2022 · 0 comments · Fixed by #654
Assignees
Labels
enhancement New feature or request

Comments

@seanpreston
Copy link
Contributor

seanpreston commented Jun 9, 2022

Right now a freshly deployed Fidesops instance has no way to process privacy requests until a Policy is configured. We should ship two default Policies with the keys download and delete to correspond with the Privacy Centre's expectations. Policy.drp_action should also be set appropriately for both policies.

We can create both of these policies as a migration to be run when FIdesops starts up.

@seanpreston seanpreston added the enhancement New feature or request label Jun 9, 2022
@pattisdr pattisdr self-assigned this Jun 13, 2022
seanpreston pushed a commit that referenced this issue Jun 16, 2022
* WIP: Add a data migration that autogenerates a default 'download' and 'delete' policy.

* Bump downrev and add logging for data migration steps.

* Try importing models from db.base.

* Use the connection currently being used to emit SQL to the database.

* Skip adding default policies to test database.

* Refactor so we're querying in SQL and not relying on SQLAlchemy models.

* Add default policies to policy guides and clarify that the TESTING env variable is primarily set by pytest.

* Update docs/fidesops/docs/guides/policies.md

Co-authored-by: Cole Isaac <[email protected]>

Co-authored-by: Cole Isaac <[email protected]>
sanders41 pushed a commit that referenced this issue Sep 22, 2022
* WIP: Add a data migration that autogenerates a default 'download' and 'delete' policy.

* Bump downrev and add logging for data migration steps.

* Try importing models from db.base.

* Use the connection currently being used to emit SQL to the database.

* Skip adding default policies to test database.

* Refactor so we're querying in SQL and not relying on SQLAlchemy models.

* Add default policies to policy guides and clarify that the TESTING env variable is primarily set by pytest.

* Update docs/fidesops/docs/guides/policies.md

Co-authored-by: Cole Isaac <[email protected]>

Co-authored-by: Cole Isaac <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants