## Context This issue covers the Create, Edit, and Delete flows for all three repository types in Artifact Registry: hosted, remote, and virtual. The Read experience is covered in the repository detail page design (https://gitlab.com/gitlab-org/gitlab/-/work_items/594712). ## Scope **In scope** * Create repository flow for all three repo types (hosted, remote, virtual) * Edit repository flow * Delete repository flow **Out of scope** * Access control and permissions configuration (separate issue) * Lifecycle and retention policy configuration (separate issue) * Soft delete and artifact recovery (connected to lifecycle and retention policy work, separate issue) * PyPI, NuGet, and additional formats (v1.0+) ## Users and goals **Intended users:** Platform engineers **Primary need:** Platform engineers need to be able to set up and configure repositories efficiently, with clear guidance on configuration options and the consequences of each setting, so they can onboard teams and manage artifact infrastructure confidently. **Relevant JTBDs:** * **Configure team environment:** When setting up a new artifact infrastructure, I want to be confident my environment is configured properly and securely, so I can ensure consistent and secure development processes in my team. * **Minimize artifact system maintenance**: When managing dependency and artifact infrastructure, I want to minimize routine system upkeep like upgrades and cleanup, so I can focus on other higher value priorities. See https://gitlab.com/gitlab-org/gitlab/-/work_items/585652+ for the full vision. ## Design proposal ### :point_right: Create :frame_photo: [Figma file](https://www.figma.com/design/b5gaaEDjfxZbphoRQ3jVGv/AM-concepting?node-id=849-46650&t=8u60A0L75UXGECx9-0) | :robot: [AI prototype](https://gitlab-org.gitlab.io/ci-cd/package-stage/artifact-registry-design-proposal/index.html) <table> <tr> <th colspan="2"> Entry point - `Repo list` (https://gitlab.com/gitlab-org/gitlab/-/work_items/594412) </th> </tr> <tr> <td> {width="900" height="587"} </td> <td> * Create repository button on the repo listing page. * Dropdown options: * Hosted repository * Remote repository * Virtual repository * Selecting an option navigates to the corresponding create form page below. </td> </tr> </table> ##### Common patterns across all repository types: **Page header** * **Page title**: `Create [type] repository` * **Page description**: A one-line description explaining the repository type **Form fields** * **Format** (dropdown) * Format icon displayed alongside option. * Helper text * **Repository name** (text input) * Placeholder: `my-[type]-repository` * Helper text * Validation (if duplicate detected) * **Description** (textarea, optional) * **Visibility level** (radio group) * Private (default) * Internal * Public **Form actions** * `Create repository` - navigates to new repo detail page on success * `Cancel` - returns to repo listing page <table> <tr> <th> Create `hosted` repo </th> <th> Create `remote` repo </th> <th> Create `virtual` repo </th> </tr> <tr> <td> {width="3343" height="2179"} </td> <td> {width="1911" height="1370"} </td> <td> {width="840" height="547"} </td> </tr> <tr> <td rowspan="2"> :robot: [AI prototype](https://gitlab-org.gitlab.io/ci-cd/package-stage/artifact-registry-design-proposal/repositories/hosted/create.html) No additional fields beyond the [common patterns](https://gitlab.com/gitlab-org/gitlab/-/work_items/598033#common-patterns-across-all-repository-types) above. </td> <td rowspan="2"> :robot: [AI prototype](https://gitlab-org.gitlab.io/ci-cd/package-stage/artifact-registry-design-proposal/repositories/remote/create.html) Additional form fields beyond the [common patterns](https://gitlab.com/gitlab-org/gitlab/-/work_items/598033#common-patterns-across-all-repository-types) above: **Source** * **URL** (text input) * **Authentication** {width="792" height="285"} (optional) * Username (text input) * Token or password (password input) * **Test upstream connection** (button) * Triggers a connection check against the entered URL and credentials if provided * **Artifact caching period** (number input) * in hours, defaults to 24 * **Metadata caching period** (number input) * in hours, defaults to 24 </td> <td> :robot: [AI prototype](https://gitlab-org.gitlab.io/ci-cd/package-stage/artifact-registry-design-proposal/repositories/virtual/create.html) Additional form fields beyond the [common patterns](https://gitlab.com/gitlab-org/gitlab/-/work_items/598033#common-patterns-across-all-repository-types) above: **Format** * Additional helper text specific to virtual: "Only repositories of the same format can be added as sources." **Source repositories card** * **Card header**: `[Format] repositories` + counter `[n] of 20` (https://gitlab.com/gitlab-org/gitlab/-/work_items/594712#note_3262304854) * **Card description** * **Add Repository button** **Empty state** (no repositories added yet) * Inline message </td> </tr> <tr> <td> **Add repository interaction** 1. **Search state** {width="900" height="127"} * Search input appears inline within the card after "Add repository" button clicks 2. **Select a repo** {width="900" height="383"} * Dropdown shows matching existing hosted and remote repositories of the same format * Each result shows: repo name, URL (for remote), type badge (Hosted / Remote) {width="900" height="154"} * Multiple repositories can be selected - appear as removable token pills in the search input * Add button - confirms selection and adds to the list * Cancel button - dismisses the search input without adding 3. **Populated source list & reorder** {width="900" height="351"} * Order * Up/down chevron buttons on the left of each row * First row: up chevron is disabled * Last row: down chevron is disabled * Repository * Name * URL + connection status indicator (remote repo only) * Type (Remote/Hosted) * Size * Actions: * Edit (icon button) * Remove (icon button) * More icon and overflow menu: * Move to start of list (not for the first row) * Move to end of list (not for the last row) * Clear cache (remote repo only) * {width="900" height="428"} * Drag handle on each row for reordering **Future consideration** The drag-and-drop component is not yet accessible in the design system. We could reconsider using it when https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/work_items/3485 is built. {width="900" height="310"} </td> </tr> </table> ### :point_right: Read :frame_photo: [Figma file](https://www.figma.com/design/b5gaaEDjfxZbphoRQ3jVGv/AM-concepting?node-id=854-50668&t=8u60A0L75UXGECx9-0) Please see https://gitlab.com/gitlab-org/gitlab/-/work_items/594712+ ### :point_right: Edit (Update) :frame_photo: [Figma file](https://www.figma.com/design/b5gaaEDjfxZbphoRQ3jVGv/AM-concepting?node-id=854-50678&t=8u60A0L75UXGECx9-0) | :robot: [AI prototype](https://gitlab-org.gitlab.io/ci-cd/package-stage/artifact-registry-design-proposal/repositories/hosted/?name=com.company.payments%3Apayment-core&format=Maven) ##### Common patterns across all repository types All three edit forms share the following differences from the create form: * **Page header:** Page title: `Edit [type] repository` with format icon. * **Format:** Not shown. Cannot be changed after creation. * **Repository name:** Shown as a disabled text input, pre-filled with the current name. Not editable (see https://gitlab.com/gitlab-org/gitlab/-/work_items/592582+) * **Description**: Pre-filled with current value if set * **Visibility level**: Pre-selected to current value, editable * **Form actions** * Save changes * Cancel: Returns to repo detail page <table> <tr> <th> Edit `hosted` repo </th> <th> Edit `remote` repo </th> <th> Edit `virtual` repo </th> </tr> <tr> <td> {width="1030" height="667"} </td> <td> {width="976" height="635"} </td> <td> {width="900" height="589"} </td> </tr> <tr> <td> :robot: [AI prototype](https://gitlab-org.gitlab.io/ci-cd/package-stage/artifact-registry-design-proposal/repositories/hosted/edit.html?name=com.company.payments%3Apayment-core&format=Maven&visibility=private) No additional fields beyond the [common edit patterns](https://gitlab.com/gitlab-org/gitlab/-/work_items/598033#common-patterns-across-all-repository-types-1) above. </td> <td> :robot: [AI prototype](https://gitlab-org.gitlab.io/ci-cd/package-stage/artifact-registry-design-proposal/repositories/remote/edit.html?name=com.company.payments%3Apayment-core&format=Maven&visibility=public&url=https%3A%2F%2Frepo1.maven.org%2Fmaven2%2F) See the [common edit patterns](https://gitlab.com/gitlab-org/gitlab/-/work_items/598033#common-patterns-across-all-repository-types-1) above, and: **Source** Pre-filled with previously saved values. Except token/ password is always empty, credentials are not surfaced back for security reasons. </td> <td> :robot: [AI prototype](https://gitlab-org.gitlab.io/ci-cd/package-stage/artifact-registry-design-proposal/repositories/virtual/edit.html?name=com.company.ml%3Amodel-serving&format=Maven&visibility=private&desc=Single%20endpoint%20for%20resolving%20Maven%20dependencies%20across%20internal%20and%20upstream%20sources.&repos=%5B%7B%22name%22%3A%22maven-central%22%2C%22url%22%3A%22https%3A%2F%2Frepo1.maven.org%2Fmaven2%2F%22%2C%22type%22%3A%22Remote%22%2C%22visibility%22%3A%22public%22%2C%22size%22%3A%22570%20MB%22%7D%2C%7B%22name%22%3A%22Spring%20repository%22%2C%22url%22%3A%22https%3A%2F%2Frepo.spring.io%2Fmilestone%2F%22%2C%22type%22%3A%22Remote%22%2C%22visibility%22%3A%22public%22%2C%22size%22%3A%22345%20MB%22%7D%2C%7B%22name%22%3A%22internal-release%22%2C%22url%22%3A%22%22%2C%22type%22%3A%22Hosted%22%2C%22visibility%22%3A%22internal%22%2C%22size%22%3A%2268%20MB%22%7D%2C%7B%22name%22%3A%22shared-libs%22%2C%22url%22%3A%22%22%2C%22type%22%3A%22Hosted%22%2C%22visibility%22%3A%22private%22%2C%22size%22%3A%2268%20MB%22%7D%5D) See the [common edit patterns](https://gitlab.com/gitlab-org/gitlab/-/work_items/598033#common-patterns-across-all-repository-types-1) above. The source repositories card is the same as the create form populated state, pre-filled with existing sources. </td> </tr> </table> ### :point_right: Delete :frame_photo: [Figma file](https://www.figma.com/design/b5gaaEDjfxZbphoRQ3jVGv/AM-concepting?node-id=976-18006&t=8u60A0L75UXGECx9-0) <table> <tr> <th>Entry point</th> <th>Delete modal</th> <th>Post-deletion</th> </tr> <tr> <td> {width="626" height="434"} </td> <td> {width="900" height="320"} {width="900" height="321"} </td> <td> {width="900" height="587"} </td> </tr> <tr> <td> * Delete action is accessible via the kebab menu on the repo detail page. * Visible to Manager and Admin roles only. </td> <td> * **Modal title**: "Delete repository?" * **Type-specific copy**: * Hosted: This action permanently deletes the repository and all of its artifacts. If this repository is connected to a virtual repository, the virtual repository loses access to this repository and its artifacts. * Remote: This action permanently deletes the repository and all its cached artifacts. Any virtual repositories that include this repository will lose this source and may return errors until reconfigured. * Virtual: This action permanently deletes the repository and its configuration. The hosted and remote repositories it aggregates are not affected. Cached content from this virtual repository will be automatically removed based on your retention policy settings. * **Confirmation input**: "Type the repository name below to confirm:" with the repo name shown as a code label above the text input * **Delete repository button**: danger style, disabled until the typed name matches exactly * **Cancel button**: dismisses the modal </td> <td> * User is redirected to the repo listing page * Dismissible success toast at the top: "\[repo-name\] was successfully deleted." * Repo count updates accordingly * If the deleted repo was the last one, the repo listing empty state is shown </td> </tr> </table> ## Relevant links * Repository detail page: #594712 * Repository listing: #594412 * Glossary: [Key terms](https://gitlab.com/gitlab-org/ci-cd/package-stage/unified-artifact-management/-/blob/main/glossary.md?ref_type=heads) * AR MVP concept flow: [FigJam](https://www.figma.com/board/L8qdx9PsEPZ7y0BzJ3K6cM/Artifact-Registry-concept-flow?node-id=342-325)