WIP: Conditional mocking of admin mode in specs based on directory

mentioned in merge request gitlab-org/gitlab!27405 (closed)

added 1 commit

5edc0504 - Add missing paths to be allowed for mocking

Compare with previous version

added 236 commits

5edc0504...adfd65e5 - 232 commits from branch master
27da8ced - Add cost factor fields to ci runners
e506176d - Merge branch '210570-add-cost-factors-to-ci-runners' into 'master'
9a500984 - Conditional mocking of admin mode in specs based on directory
d61ed565 - Add missing paths to be allowed for mocking

Compare with previous version

mentioned in issue gitlab-org/gitlab#212434 (closed)

added 184 commits

d61ed565...84360544 - 182 commits from branch master
66c954c1 - Conditional mocking of admin mode in specs based on directory
e9e00473 - Add missing paths to be allowed for mocking

Compare with previous version

@dlouzan I'd be okay with this approach and then removing a directory from the list in each merge request. But let's get some thoughts from the Quality team for this.

@rymai Would you be okay with this kind of approach? The goal is to have all admin specs have a tag :enable_admin_mode so they run with elevated privileges. The "admin mode" is currently enabled for all specs, but ideally we'd only have that for the specs requiring it. This is what @dlouzan is working on.

For most specs, it's just adding the :enable_admin_mode tag to make them pass, but some require more effort. Doing it all at once results in a huge MR that 's hard to review (gitlab-org/gitlab!27405 (closed)). So with this, the work could be split up by folder, do you think that makes sense?