Skip to content

Add security scanners column into

What does this MR do?

Add security scanners column into approval_project_rules table.

Related issue: #334935 (closed)

Migrate:

bundle exec rails db:migrate
== 20210708202548 AddScannersColumnToApprovalProjectRules: migrating ==========
-- add_column(:approval_project_rules, :scanners, :text, {:array=>true, :default=>["sast", "secret_detection", "dependency_scanning", "container_scanning", "cluster_image_scanning", "dast", "coverage_fuzzing", "api_fuzzing"], :null=>false})
   -> 0.0036s
== 20210708202548 AddScannersColumnToApprovalProjectRules: migrated (0.0037s) =

Rollback:

bundle exec rails db:rollback
== 20210708202548 AddScannersColumnToApprovalProjectRules: reverting ==========
-- remove_column(:approval_project_rules, :scanners)
   -> 0.0024s
== 20210708202548 AddScannersColumnToApprovalProjectRules: reverted (0.0025s) =

Database-lab:

exec ALTER TABLE approval_project_rules ADD COLUMN scanners text[] DEFAULT '{sast,secret_detection,dependency_scanning,container_scanning,cluster_image_scanning,dast,coverage_fuzzing,api_fuzzing}'::text[] NOT NULL
Session: 5184
The query has been executed. Duration: 24.618 ms (edited) 

Screenshots or Screencasts (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

  • 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 Zamir Martins

Merge request reports