Prepare for dropping REST support and adding analyzers configuration
What does this MR do?
This change is dependent on !41995 (merged) being merged. While the REST POST will still work with this code, it won't properly handle not writing default values, so we should not merge this until we have switched to using the GraphQL mutation.
With the implementation of the GraphQL mutation, we will receive the default values for the supplied variables, which allows us to avoid making an expensive call to parse the SAST vendored template to determine them.
This also makes the implementation of Store the information about analyzers in .gitlab-ci.yml file simpler.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
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