-
Notifications
You must be signed in to change notification settings - Fork 28
chore: store provenance asset info #975
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: main
Are you sure you want to change the base?
Conversation
7ced4d8
to
03ae1b2
Compare
03ae1b2
to
ede14d0
Compare
ede14d0
to
e708d81
Compare
Signed-off-by: Ben Selwyn-Smith <benselwynsmith@googlemail.com>
Signed-off-by: Ben Selwyn-Smith <benselwynsmith@googlemail.com>
Signed-off-by: Ben Selwyn-Smith <benselwynsmith@googlemail.com>
e708d81
to
25bf1c1
Compare
Signed-off-by: Ben Selwyn-Smith <benselwynsmith@googlemail.com>
Signed-off-by: Ben Selwyn-Smith <benselwynsmith@googlemail.com>
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 would be good to add an integration test that checks the values stored in the Provenance
and ProvenanceAvailableFacts
tables.
if not provenance_info or not provenance_info.provenance_payload or inferred: | ||
return CheckResultData( | ||
result_tables=[ | ||
ProvenanceAvailableFacts( |
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 like we are not storing any useful info, so I think we can skip this? Or am I missing something here? 🤔
This PR adds provenance asset info to the database alongside the provenance it identifies. This was previously removed during refactoring.
Closes #819