Skip to content

Fix unverified badge

What does this MR do and why?

Fixes an issue where verified namespaces in a SM instance cannot update to UNVERIFIED

References

#578844

How to set up and validate locally

  1. As an admin, run the following mutation in graphql-explorer if you don't have any verified namespaces. If you do, skip to step 2.
  mutation {
    verifiedNamespaceCreate(
      input: {
        namespacePath: "root"
        verificationLevel: VERIFIED_CREATOR_SELF_MANAGED
      }
    ) {
      errors
    }
  }
  1. Try to update to UNVERIFIED
mutation {
    verifiedNamespaceCreate(
      input: {
        namespacePath: "root"
        verificationLevel: UNVERIFIED
      }
    ) {
      errors
    }
  }
Before

After - NO ERROR! ☺️

{
  "data": {
    "verifiedNamespaceCreate": {
      "errors": [
        "Cannot use unverified on a non-Gitlab.com instance.Use `VERIFIED_CREATOR_SELF_MANAGED`."
      ]
    }
  },
  "correlationId": "01K8TKRVC445EQFM4Q2YG9ZACC"
}
{
  "data": {
    "verifiedNamespaceCreate": {
      "errors": []
    }
  },
  "correlationId": "01K8TKVHDZMXHB5Y32GQFVGCD1"
}

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.

Merge request reports

Loading