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

Refacto: separate storage backend, merge client_interface and trow_server into "registry" #382

Merged
merged 15 commits into from
May 15, 2024

Conversation

awoimbee
Copy link
Collaborator

I've been working on this for a while...

Initial goal: separate all storage operations from trow_server so features such as tiered storage and s3 backend could be added later.

Final state:

  • storage operations are united in storage.rs
  • tests don't require neither subprocesses nor to be ran sequentially anymore
  • trow_server and registry_interface are united as registry
  • update deps

I think the next step is to add a database, working around the "manifest_history" files is not straightforward.
This PR breaks compatibility with the data dirs of old trow versions.

@awoimbee awoimbee requested a review from amouat May 13, 2024 11:52
@awoimbee awoimbee self-assigned this May 13, 2024
@awoimbee awoimbee force-pushed the aw/separate-storage-backend branch from 2f86b03 to 8c87ce8 Compare May 13, 2024 20:28
@awoimbee
Copy link
Collaborator Author

I want to get this over with, I will fix the OCI compliance tests later

@awoimbee awoimbee force-pushed the aw/separate-storage-backend branch from 91732c2 to 41bfc04 Compare May 15, 2024 14:21
@awoimbee awoimbee merged commit e09a0a1 into main May 15, 2024
4 of 5 checks passed
@awoimbee awoimbee deleted the aw/separate-storage-backend branch May 15, 2024 14:31
@amouat
Copy link
Contributor

amouat commented May 15, 2024

Yeah go for it. I don't really have time to review atm unfortunately.

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.

2 participants