-
Notifications
You must be signed in to change notification settings - Fork 78
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
LA-41 Update POST endpoints for data categories, subjects and uses for new taxonomy functionality #5468
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
fides
|
Project |
fides
|
Branch Review |
refs/pull/5468/merge
|
Run status |
|
Run duration | 00m 39s |
Commit |
|
Committer | Catherine Smith |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
0
|
|
0
|
|
0
|
|
4
|
Upgrade your plan to view test results. | |
View all changes introduced in this branch ↗︎ |
model.active is False, | ||
) | ||
if disabled_resource_with_name: | ||
return model.update(db=db, data=disabled_resource_with_name, active=True) # type: ignore[union-attr] |
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.
What happens if the incoming data
doesn't match the DB model we're reactivating? Should we pass in the incoming data
instead of the disabled_resource_with_name
?
return model.update(db=db, data=disabled_resource_with_name, active=True) # type: ignore[union-attr] | |
return model.update(db=db, data=data, active=True) # type: ignore[union-attr] |
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.
Yes good call!
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.
Thanks for making the recommended changes, approved!
fides
|
Project |
fides
|
Branch Review |
main
|
Run status |
|
Run duration | 00m 37s |
Commit |
|
Committer | Catherine Smith |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
0
|
|
0
|
|
0
|
|
4
|
Upgrade your plan to view test results. | |
View all changes introduced in this branch ↗︎ |
Closes https://ethyca.atlassian.net/browse/LA-41
Description Of Changes
Update POST endpoints for data categories, subjects and uses for new taxonomy functionality. Specifically enables us to do 2 things:
Code Changes
Steps to Confirm
/data_use
, POST/data_category
, and POST/data_subejct
. Confirm that you can create a resource without having to specify a fides keyPre-Merge Checklist
CHANGELOG.md
main
downgrade()
migration is correct and works