Loading
feat(datastore): container virtual upstream store types and list read part 1/15 (S17 Phase 6 plan: 42/42)
Why
The container family is the only format whose upstream-association rule admits a mix: docker and oci share one junction table, so either is associable on a virtual repository of the other. Until the store lands, a container virtual repository is creatable but not configurable.
This part ships the store's types, its constructor, and the one read the management API serves.
The stack
Fifteen parts, each stacked on the last, each green on its own, reviewed in this order. Changed lines counts added plus deleted.
The delete guard in part 9 lands before the routes in part 11, so no window exists where a container association is writable without the refusal that protects it.
Related to #314 (closed)
Edited by Hayley Swimelar