Migrate ProjectSettingsUpdate mutation off AvailableServices

Matthias Käpplerrequested to merge
542422-project-update-mutation into master

What does this MR do and why?

Migrate ProjectSettingsUpdate mutation off AvailableServices, which we are phasing out. This is part of Replace methods that check for AddOnPurchases (#542422 - closed).

This is a refactor and not user-facing, so I left the existing semantics intact, which are:

  • on gitlab.com, this path is always enabled.
  • on SM/Dedicated, an instance-wide lookup for add-ons is made.

This second part is now implemented using ::GitlabSubscriptions::AddOnPurchase.find_for_active_duo_add_ons(:instance).

References

#542422 (closed)

How to set up and validate locally

  1. Make sure GITLAB_SIMULATE_SAAS is falsey
  2. Send a projectSettingsUpdate mutation e.g. via /-/graphql-explorer

Without Duo purchases ⛔

image

With Duo purchases ✅

image

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 #542422 (closed)

Edited by Matthias Käppler

Merge request reports