-
Notifications
You must be signed in to change notification settings - Fork 43
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
fix: resolve tag conflicts for versioned artifacts #920
Conversation
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
Your patch looks good overall. Just added some "nits". Feel free to take them or continue as-is if you want. |
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
Thanks, I've just addressed your feedback 👍 |
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.
looking good, some nits inline
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
@jhrozek - addressed your feedback, so feel free to re-review 👍 |
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.
thank you for the fix!
On each publish event for a package/artifact we insert a new record in artifact_versions which has a given set of tags associated with it. After a while we end up having multiple records that share the same tag entries (or one is a subset of the other) which is wrong given that a tag should be matched to only one image digest.
The following PR introduces the idea of searching for all existing entries that match the incoming tag value in their Tags field. If found, the existing artifact is updated by removing the incoming tag from its tags column.
Fixes #814