Explore enabling top level group creation on Staging
Top level group creation via API is blocked on ::Gitlab.com? which includes Staging as well. It affects several specs:
qa/qa/specs/features/api/1_manage/bulk_import_group_spec.rbqa/qa/specs/features/api/1_manage/bulk_import_project_spec.rbqa/qa/specs/features/browser_ui/1_manage/group/bulk_import_group_spec.rbqa/qa/specs/features/ee/browser_ui/1_manage/group/prevent_forking_outside_group_spec.rbqa/qa/specs/features/ee/browser_ui/5_package/dependency_proxy_sso_spec.rbqa/qa/specs/features/ee/browser_ui/fulfillment/purchase/purchase_ci_spec.rbqa/qa/specs/features/ee/browser_ui/fulfillment/purchase/upgrade_group_spec.rb
Some of them are configured to enable top_level_group_creation_enabled before the test and disabling it after. This results in transient 403 errors similar to gitlab-org/gitlab#342491 (closed) since multiple tests are toggling the same FF during test run.
The issue is to explore if the FF can be enabled on Staging by default and clean up Runtime::Feature.enable(:top_level_group_creation_enabled) calls or maybe there are other solutions. Alternatively the specs could be quarantined specifically on Staging/Production.
See @chloeliu's suggestion below:
There are lots of tests in Fulfillment team that require a top-level group, we ended up with a workaround to use either API or UI based the FF's status on staging