Set FF allow_duo_base_access to true

Lukas Wankorequested to merge
lw/536311-set-default-allow-duo-base-access-to-true into master

What does this MR do and why?

The FF allow_duo_base_access is currently disabled by default, and also on production, it is set to false. It controls whether the customer has access to the user interface for Duo Core management. Soon, we want to enable the FF on production for GitLab.com and for Self-Managed, and at some point, we want to remove the FF entirely from the codebase.

I suggest setting the default for this FF to true to ensure all GitLab.com Self-Managed release >= 18.0 instances will also have access to the user interface after the removal. Then we can follow the following steps:

Steps

  1. Disable the FF for production.
  2. Deploy this merge request.
  3. Enable the FF for GA for Duo Core.
  4. Remove the FF
    • All Self-Managed customers with release >= 18.0 will have access to Duo Core's user interface, even if the removal is not included in the release.

References

Screenshots or screen recordings

Before After

How to set up and validate locally

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.

Edited by Lukas Wanko

Merge request reports