Skip to content

Remove User#triggers dependent: :destroy

What does this MR do?

This does not appear to be necessary. It was first added in gitlab-foss!9713 (comment 24835526) and there does not appear to be any justification for this as there is already a cascading foreign key delete. There don't appear to be any before_destroy or similar steps that might benefit from this dependent: :destroy so it seems safe to remove it.

We already have the FK:

ALTER TABLE ONLY ci_triggers
    ADD CONSTRAINT fk_e8e10d1964 FOREIGN KEY (owner_id) REFERENCES users(id) ON DELETE CASCADE;

Screenshots or Screencasts (strongly suggested)

How to setup and validate locally (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

Related to #339813 (closed)

Merge request reports

Loading