Show associated registries before maven upstream deletion
What does this MR do and why?
Query list of registries associated with upstream added in Adds mavenUpstreamRegistry top-level GraphQL query (!203463 - merged).
Extracts delete upstream logic & modal into a separate modal component which can be reused.
Shows names of associated registries in the modal before maven upstream deletion.
EE: true
References
- Design: #556828[DeleteUpstreamModal.png]
- Move and update delete button style on edit ups... (#565346 - closed)
Screenshots or screen recordings
| Description | Before | After |
|---|---|---|
| Default | ![]() |
![]() |
| Modal | ![]() |
|
| Modal when registries are associated | ![]() |
|
| Modal when more than 5 registries are associated | ![]() |
|
| When there are no registries associated | ![]() |
How to set up and validate locally
- Ensure you have enabled the following feature flags
$ gdk rails console
Feature.enable(:maven_virtual_registry)
Feature.enable(:ui_for_virtual_registries)
- Go to a group
- Go to
Deploy -> Virtual Registry - Create a new maven registry
- Click on the
Add upstreambutton - The required fields are
name,url. For the URL, you can usehttps://repo.maven.apache.org/maven2/ - Click on
Create upstreamand observe the list update. - Click on the pencil icon for the newly created upstream. This should take you to the edit upstream page.
- Click on
Delete upstreambutton should show modal with the registry names listed. - Create at least 5 more maven registries. Link the same upstream to each of the virtual registry.
- Clicking on
Delete upstreambutton should show modal with the registry names listed & truncated.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #556828 (closed)
Edited by Rahul Chanila





