Loading
Support custom registries for Foundational Flows
What does this MR do and why?
This MR adds support for setting custom registries for Foundational Flows in the instance admin menu of self-managed instances.
References
Screenshots or screen recordings
| Before | After | |
|---|---|---|
| Self managed admin settings http://gdk.test:3000/admin/gitlab_duo/configuration | ![]() |
![]() |
| SaaS namespace settings http://gdk.test:3000/groups/gitlab-duo/-/settings/gitlab_duo/configuration | ![]() |
![]() |
How to set up and validate locally
- If not yet merged, rebase on the backend !222281 (merged)
- Run GDK in self-managed mode
- Go to instance admin settings: http://gdk.test:3000/admin/gitlab_duo/configuration
- Add a registry e.g. "non-existing-registry.gitlab.com" and click "Save changes"
- Go to a Duo enabled project and open e.g. an issue and click on "Generate MR with Duo"
- Open the session, click on details and then on the job id
- Observe that the job failed as it could not pull from the registry
- Optionally clear the registry in the settings and run another flow observe that it pulls from registry.gitlab.com and passes.
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 #584689 (closed)
Edited by Fred de Gier






