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

Add support for multiple tags per-release #917

Open
ezekg opened this issue Nov 15, 2024 · 1 comment
Open

Add support for multiple tags per-release #917

ezekg opened this issue Nov 15, 2024 · 1 comment

Comments

@ezekg
Copy link
Member

ezekg commented Nov 15, 2024

E.g. with Docker, you may want to tag an image release as latest, 1, and 1.2, with a version of 1.2.3.

Right now, you can tag latest and that's it, which isn't conventional.

@ezekg
Copy link
Member Author

ezekg commented Jan 13, 2025

Implementation-wise, I see 2 options right now:

  1. Use a releases.tags array column with a GIST intersection constraint: ALTER TABLE releases ADD CONSTRAINT release_unique_tags_constraint EXCLUDE USING GIST (tags WITH &&). But iirc, GIST has perf gotchas.
  2. Use a release_tags table with a unique index on (key, account_id, product_id[, release_package_id]), similar to what we currently have with releases.tag. Probably the simplest solution.

I lean towards the latter.

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

No branches or pull requests

1 participant