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

[2/n] store blueprint zone image source in database #7849

Open
wants to merge 6 commits into
base: sunshowers/spr/main.wip-store-blueprint-zone-image-source-in-database
Choose a base branch
from

Conversation

sunshowers
Copy link
Contributor

@sunshowers sunshowers commented Mar 21, 2025

As discussed in RFD 554, we only store zone image artifact hashes in the database, and look up versions via a left join (so it is allowed to fail).

This lookup requires the kind + hash to be unique, so we add a database and app-level constraint for that, mirroring the constraint implemented in oxidecomputer/tufaceous#16.

Also change tuf_artifact's version field to 64 bytes per this discussion.

Depends on:

Created using spr 1.3.6-beta.1
Created using spr 1.3.6-beta.1
Created using spr 1.3.6-beta.1
@sunshowers sunshowers changed the title [wip] store blueprint zone image source in database store blueprint zone image source in database Mar 21, 2025
@sunshowers sunshowers marked this pull request as ready for review March 21, 2025 09:59
Created using spr 1.3.6-beta.1
@sunshowers
Copy link
Contributor Author

Ah, I need to update the fake TUF repo generation to ensure that (kind, hash) is actually unique. Moving to draft for now.

@sunshowers sunshowers marked this pull request as draft March 21, 2025 10:13
Created using spr 1.3.6-beta.1
@sunshowers sunshowers changed the base branch from main to sunshowers/spr/main.wip-store-blueprint-zone-image-source-in-database March 27, 2025 02:38
@sunshowers sunshowers changed the title store blueprint zone image source in database [2/n] store blueprint zone image source in database Mar 27, 2025
Created using spr 1.3.6-beta.1
@sunshowers sunshowers marked this pull request as ready for review March 27, 2025 18:23
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.

1 participant