Update PrAT feature check to return false for gitlab.com
requested to merge 235736-follow-up-from-enable-resource_access_token-feature-flag-by-default into master
What does this MR do?
Follow-up to !39287 (comment 394758746)
Closes #235736 (closed)
Because we are only rolling this feature out to self-managed instances in %13.3 we want to add a strict ban for gitlab.com. The same check added in this MR already exists at app/helpers/projects_helper.rb#L776.
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- Developer facing change, not needed
- [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
-
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec
- [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Edited by Peter Leitzen