Skip to content
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

refactor(scanner)!: Align provenance storages on write instead of put #8322

Merged
merged 1 commit into from
Feb 21, 2024

Conversation

sschuberth
Copy link
Member

Say write instead of put to match read functions and to align with the ScanStorage interfaces.

…put`

Say `write` instead of `put` to match `read` functions and to align with
the `ScanStorage` interfaces.

Signed-off-by: Sebastian Schuberth <[email protected]>
@sschuberth sschuberth requested a review from a team as a code owner February 21, 2024 10:24
@sschuberth
Copy link
Member Author

As discussed, @mnonnenmacher.

* Put the resolution [result] for the [root] provenance into the storage. If the storage already contains an entry
* for [root] it is overwritten.
* Write the resolution [result] for the [root] provenance into the storage. If the storage already contains an
* entry for [root] it is overwritten.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

out of scope: I've recently mentioned (slack) the constraint violations in the logs which occur when the entry already exists. Without looking into it, I guess that it's actually not overwritten but ignored in the Postgres based implementation.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fviernau I'm only aware of possible constraint violations related to storing scan results, but not for provenance resolution results.

@sschuberth sschuberth merged commit 4cda5b4 into main Feb 21, 2024
20 of 21 checks passed
@sschuberth sschuberth deleted the provenance-put-vs-write branch February 21, 2024 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants