## Summary CRUD for remote and virtual repositories on the management API, per [ADR-009](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/artifact_registry/decisions/009_api_design/#repository-level-apis): the non-hosted polymorphic `settings` (remote upstream URL, auth, cache TTLs; virtual upstream associations), upstream management routes, and connection test. Phase 1 shipped the shared repository CRUD with hosted-only rows; this phase lifts the non-hosted rejection. ## Gated on - **S13 Virtual and remote foundation** and the format slices: S14-S16 (remote), S30-S32 (virtual). This phase patches the [S17 spec](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/docs/specs/S17-rest-management-api.md) and follows the repo gate: spec MR, plan MR, implementation. Part of [&22341](https://gitlab.com/groups/gitlab-org/-/work_items/22341). ## Workstream status (2026-08-25) The graph is a ledger of work in progress and work to be done: a step's node leaves the graph when its merge request merges, and the Merge request status table below keeps the full step-to-MR record, merged rows included. Reading the colors, green nodes have an open merge request and link to it, amber nodes are being implemented but their merge requests have not opened yet, grey nodes are planned, red nodes are blocking follow-ups, and blue nodes are slices outside this issue's ownership whose schema migrations gate the virtual steps. Edges are the [plan's dependency graph](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/docs/plans/2026-08-13-s17-phase6-virtual-remote-repositories.md#implementation-steps) among the remaining nodes, plus the four slice edges, so every edge shown is an unsatisfied dependency. Blocking follow-ups join the map when they are filed and carry no plan edges, so the step each one holds is named in the external gates below. A follow-up leaves the map when the step it held merges, and joins the follow-up list until it closes. ### Dependency graph ```mermaid graph TD S36["Step 36: Virtual create and delete: Maven"] S37["Step 37: Virtual create and delete: npm"] S38["Step 38: Virtual create and delete: container"] S39["Step 39: Maven virtual upstream store and the delete-side guard"] S40["Step 40: Upstream association routes: Maven"] S41["Step 41: Upstream associations: npm"] S42["Step 42: Upstream associations: container"] EXTS30["S30 Maven virtual slice (#289)"] EXTS31["S31 npm virtual slice (#290)"] EXTS32["S32 container virtual slice (#291)"] S36 --> S40 S37 --> S41 S38 --> S42 S39 --> S40 S40 --> S41 S40 --> S42 EXTS30 --> S36 EXTS30 --> S39 EXTS31 --> S37 EXTS32 --> S38 click EXTS30 "https://gitlab.com/gitlab-org/ops/artifact-registry/-/issues/289" click EXTS31 "https://gitlab.com/gitlab-org/ops/artifact-registry/-/issues/290" click EXTS32 "https://gitlab.com/gitlab-org/ops/artifact-registry/-/issues/291" classDef stOpen fill:#c8e6c9,stroke:#2e7d32,color:#1b5e20 classDef stInBuild fill:#ffecb3,stroke:#ff8f00,color:#ff6f00 classDef stPlanned fill:#f5f5f5,stroke:#9e9e9e,color:#424242 classDef stBlocking fill:#ffcdd2,stroke:#c62828,color:#b71c1c classDef stExternal fill:#d6e4ff,stroke:#3f51b5,color:#1a237e class S36,S37,S38,S39,S40,S41,S42 stPlanned class EXTS30,EXTS31,EXTS32 stExternal ``` Beyond the four slice edges the diagram carries, the plan names these external gates per step: - **Step 33** has merged, gitlab-org/ops/artifact-registry!1805+s. It landed ahead of the deploy-ordering decision under the merge-throughput ruling, so both of its blocking follow-ups outlived it. Neither holds an unmerged step now, so both have left the map for the follow-up list. While gitlab-org/ops/artifact-registry#755+s is open the deploy-ordering question is unresolved on the record, and the issue closes on that answer rather than on a merge. All three remote bulk passes have now merged and none of them satisfies the `delete_all` contract, which defines completion as emptiness at acceptance time, so gitlab-org/ops/artifact-registry#738+s stays open as well. The fail-closed worker fix those passes needed is on main as gitlab-org/ops/artifact-registry!1736+s. - **Step 34** has merged, gitlab-org/ops/artifact-registry!1841+s. It validates the update's `url` at exact parity with create through the shared decode and parse path and adds no fetch-time covers, so the spec self-conflict gitlab-org/ops/artifact-registry#715+s records holds no step and sits on the non-blocking list below. What its merge opened was a deploy-order window on main: while the container remote bulk pass was unmerged, a docker or oci URL change reached a worker arm that was not deployed, failed closed, and parked on River retries. That window closed when the bulk pass merged, gitlab-org/ops/artifact-registry!1805+s. - **Step 35** was stacked rather than gated. It merged into step 20's branch, gitlab-org/ops/artifact-registry!1900+s, and reached main when that branch did, gitlab-org/ops/artifact-registry!1748+s. The stack is how its plan dependency on step 20 was satisfied. - **Steps 36-39** wait on their format's virtual schema migration, which ships in the slice the diagram now links. The three slices sit at different stages. S31's spec is merged as `docs/specs/S31-npm-virtual.md`, S32's is in review as gitlab-org/ops/artifact-registry!972+s, and S30 has no spec at all, because gitlab-org/ops/artifact-registry#284+s is still open. No migration from any of the three is on main. - **Steps 40, 41, and 42** inherit those gates through the virtual create steps they follow. - Builders for **Steps 36-39** all exited without an artifact and returned the same two options, ship the slice or amend the plan to drop the schema dependency. Those four steps hold until that ruling lands. Non-blocking follow-ups filed against this phase carry no graph membership: gitlab-org/ops/artifact-registry#697+s, gitlab-org/ops/artifact-registry#698+s, gitlab-org/ops/artifact-registry#706+s, gitlab-org/ops/artifact-registry#707+s, gitlab-org/ops/artifact-registry#715+s, gitlab-org/ops/artifact-registry#733+s, gitlab-org/ops/artifact-registry#734+s, gitlab-org/ops/artifact-registry#735+s, gitlab-org/ops/artifact-registry#738+s, gitlab-org/ops/artifact-registry#742+s, gitlab-org/ops/artifact-registry#743+s, gitlab-org/ops/artifact-registry#744+s, gitlab-org/ops/artifact-registry#754+s, and gitlab-org/ops/artifact-registry#755+s. Steps 1 through 35 are on main at `f60ca64e3`, and no step merge request is open. The seven that remain, steps 36 through 42, all hold on the virtual schema gate, directly or through the create step each one follows. ### Merge request status | Step | Reviewer | Status | Merge request | | --- | --- | --- | --- | | 1 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1568+s | | 2 | jdrpereira | Merged | gitlab-org/ops/artifact-registry!1581+s | | 3 | radbatnag | Merged | gitlab-org/ops/artifact-registry!1571+s | | 4 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1579+s | | 5 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1585+s | | 6 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1578+s | | 7 | radbatnag | Merged | gitlab-org/ops/artifact-registry!1586+s | | 8 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1572+s | | 9 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1576+s | | 10 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1618+s | | 11 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1575+s | | 12 | vespian_gl | Merged into !1572 | gitlab-org/ops/artifact-registry!1625+s | | 13 | mkhalifa3 | Merged | gitlab-org/ops/artifact-registry!1582+s | | 14 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1629+s | | 15 | mkhalifa3 | Merged | gitlab-org/ops/artifact-registry!1749+s | | 16 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1794+s | | 17 | mkhalifa3 | Merged | gitlab-org/ops/artifact-registry!1750+s | | 18 | arpitgogia | Merged | gitlab-org/ops/artifact-registry!1799+s | | 19 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1747+s | | 20 | arpitgogia | Merged | gitlab-org/ops/artifact-registry!1748+s | | 21 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1570+s | | 22 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1632+s | | 23 | radbatnag | Merged | gitlab-org/ops/artifact-registry!1732+s | | 24 | suleimiahmed | Merged into !1618 | gitlab-org/ops/artifact-registry!1642+s | | 25 | mkhalifa3 | Merged | gitlab-org/ops/artifact-registry!1574+s | | 26 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1573+s | | 27 | mkhalifa3 | Merged | gitlab-org/ops/artifact-registry!1589+s | | 28 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1726+s | | 29 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1761+s | | 30 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1790+s | | 31 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1756+s | | 32 | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1759+s | | 33 | radbatnag | Merged | gitlab-org/ops/artifact-registry!1805+s | | 34 | jdrpereira | Merged | gitlab-org/ops/artifact-registry!1841+s | | 35 | mkhalifa3 | Merged into !1748 | gitlab-org/ops/artifact-registry!1900+s | | Follow-up | suleimiahmed | Merged | gitlab-org/ops/artifact-registry!1580+s | | Follow-up | jdrpereira | Merged | gitlab-org/ops/artifact-registry!1619+s | | Follow-up | jdrpereira | Merged | gitlab-org/ops/artifact-registry!1668+s | | Follow-up | dmeshcharakou | Merged | gitlab-org/ops/artifact-registry!1733+s | | Follow-up | 10io | Merged | gitlab-org/ops/artifact-registry!1752+s | | Follow-up | 10io | Merged | gitlab-org/ops/artifact-registry!1791+s | | Follow-up | 10io | Merged | gitlab-org/ops/artifact-registry!1796+s | | Follow-up | vespian_gl | Merged | gitlab-org/ops/artifact-registry!1846+s | | Follow-up | unassigned | Merged | gitlab-org/ops/artifact-registry!1902+s |