Repository navigation
refactor: organize model registry and infrastructure packages - #4
Merged
WaVEV merged 1 commit intoSep 29, 2026
Merged
Conversation
WaVEV
marked this pull request as ready for review
September 27, 2026 21:21
sleepyStick
approved these changes
Sep 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reorganizes the package around the model-registry store boundary. The store, repositories, persistence types, and domain errors now live under
model_registry/. MongoDB settings and reusable array-update helpers live underinfrastructure/.The idea is to organize the package by MLflow store boundary: tracking and model registry are separate interfaces, so each should own its store code and repositories. Only infrastructure they genuinely share belongs in
infrastructure/.