Skip to content

Allow a high query transaction threshold when using `all_graphql_fields_for`

Brett Walker requested to merge bw-allow-unlimited-transactions into master

What does this MR do?

When using all_graphql_fields_for for testing GraphQL queries, this pulls in all possible fields, which can result in a high number of queries. Just like we remove recursion and complexity limits (https://gitlab.com/gitlab-org/gitlab/blob/master/spec/support/helpers/graphql_helpers.rb#L131-162) when using this method.

New feature in !22497 (merged) causes the query limit to be exceeded when using all_graphql_fields_for

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

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

Merge request reports

Loading