Reschedule migration for links
What does this MR do and why?
Reschedule migration for links due to invalid data. Link to the schema
Original MR: !111454 (merged)
Related issue: #362661 (closed)
Validation based on the following errors
PG::NotNullViolation: ERROR: null value in column "url" violates not-null constraint
DETAIL: Failing row contains (255973677, 2023-03-11 17:59:05.262031+00, 2023-03-11 17:59:05.262031+00, 24042929, null, null).
undefined method `compact' for "https://eval.contrastsecurity.com/Contrast/static/ng/index.html#b9c66e72-f531-4581-b221-d020e7e2687f/applications/8f67752a-3f43-4f8e-9090-c2ee237a0769/vulns/J4NT-6T46-0VE0-OK67":String
DB migration/rollback
bundle exec rails db:migrate
main: == 20230314144640 RescheduleMigrationForLinks: migrating ======================
main: == 20230314144640 RescheduleMigrationForLinks: migrated (0.0776s) =============
ci: == 20230314144640 RescheduleMigrationForLinks: migrating ======================
ci: -- The migration is skipped since it modifies the schemas: [:gitlab_main].
ci: -- This database can only apply migrations in one of the following schemas: [:gitlab_ci, :gitlab_shared, :gitlab_internal].
ci: == 20230314144640 RescheduleMigrationForLinks: migrated (0.0058s) =============
bundle exec rails db:migrate:down:main VERSION=20230314144640
main: == 20230314144640 RescheduleMigrationForLinks: reverting ======================
main: == 20230314144640 RescheduleMigrationForLinks: reverted (0.0237s) =============
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Zamir Martins