Skip to content

Add enum to graphql mutation

What does this MR do and why?

Addressing issue.

We usually prefer to use enum in graphql mutations, so this is just a quick refactor to apply enum instead of string.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

screenshots to update an instance of Ci::Catalog::VerifiedNamespace When instance is not Gitlab.com 👇 Screenshot_2024-05-27_at_13.46.37 When passed in namespace is not a root namespace 👇 Screenshot_2024-05-27_at_13.46.54

When namespace is unknown/invalid 👇 Screenshot_2024-05-27_at_13.47.17

Success update for existing Ci::Catalog::VerifiedNamespace 👇 Screenshot_2024-05-27_at_13.47.04 Screenshot_2024-05-27_at_13.47.40

Screenshot_2024-05-27_at_13.47.49

Screenshot_2024-05-27_at_13.48.01

screenshots for new instance of Ci::Catalog::VerifiedNamespace Before calling the endpoint 👇 Screenshot_2024-05-27_at_14.01.14 When non root namespace is passed in 👇 Screenshot_2024-05-27_at_14.02.55 When invalid namespace path is passed in 👇 Screenshot_2024-05-27_at_14.07.01 Success creation 👇 Screenshot_2024-05-27_at_14.03.10 Screenshot_2024-05-27_at_14.03.19

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Edited by Kasia Misirli

Merge request reports