Finalize ArchiveAuthenticationEvents batched background migration

Jason Knablrequested to merge
578650-finalize-authn-events-worker-migration into master

What does this MR do and why?

  • Enqueue a migration to finalize the ArchiveAuthenticationEvents batched background migration
  • ArchiveAuthenticationEvents ran successfully in milestone 18.5
  • Since milestone 18.5 was a required stop I believe it is safe to finalize this migration now in 18.6 (based on the docs)
  • To confirm the migration is finished in production you can run:
/chatops run batched_background_migrations status 2001061 --database main

References

How to set up and validate locally

  • To test the finalization locally run bundle exec rails db:migrate:main

Migration output

migrate up 
% bundle exec rails db:migrate:main
main: == [advisory_lock_connection] object_id: 130400, pg_backend_pid: 45289
main: == 20251029210157 FinalizeArchiveAuthenticationEvents: migrating ==============
main: -- transaction_open?(nil)
main:    -> 0.0000s
main: == 20251029210157 FinalizeArchiveAuthenticationEvents: migrated (0.1627s) =====

main: == [advisory_lock_connection] object_id: 130400, pg_backend_pid: 45289
migrate down 
% bundle exec rails db:migrate:main
main: == [advisory_lock_connection] object_id: 130400, pg_backend_pid: 45289
main: == 20251029210157 FinalizeArchiveAuthenticationEvents: migrating ==============
main: -- transaction_open?(nil)
main:    -> 0.0000s
main: == 20251029210157 FinalizeArchiveAuthenticationEvents: migrated (0.1627s) =====

main: == [advisory_lock_connection] object_id: 130400, pg_backend_pid: 45289

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #578650 (closed)

Edited by Jason Knabl

Merge request reports