Uses different clientes to validate security merge requests
What does this MR do?
With the security development happening on GitLab, we need to validate security merge requests on Security and Dev remotes, so 'Security::MergeRequestsValidator' was modified to received different security clients.
The architecture was modified in the following way:
- Security clients were split into
Gitlab
andDev
- Gitlab client re-uses existing code on
Security::Client
-
DevClient
inherits from GitLabClient - The only difference between the clients is the
gitlab_client
- Gitlab client re-uses existing code on
- Modifies
MergeRequestsValidator
to receive a client and to decide whichprojects_to_verify
based on the client. - Modifies the security
validate
rake tasks to callMergeRequestsValidator
- If
security_remote
is disabled, it executesMergeRequestsValidator
withdev_client
only - If
security_remote
is enabled, it executesMergeRequestsValidator
withdev_client
andGitlab
client
- If
Related to #344
Edited by Mayra Cabrera