Finalize OAuth Access Tokens and Grants BBMs

Daniele Braccianirequested to merge
db/578650/finalize-authn-access-token-and-grant-bbms into master

What does this MR do and why?

Finalize OAuth Access Tokens and Grants BBMs

We ran two batched background migration to archive records in the oauth_access_tokens and oauth_access_grants tables. This commit enqueues a migration to finalize them.

Related to: #578650 (closed)

Changelog: other

Additional informations

  • Both ArchiveRevokedAccessTokens and ArchiveRevokedAccessGrants BBMs have been merged during 18.5
  • They ran successfully in 18.5. Results are available in their related issues
  • The BBMs targeted only .com, so we don't need to wait a Database required stop to finalize them
  • To confirm the migration is finished in production you can run:
# For ArchiveRevokedAccessTokens
/chatops run batched_background_migrations status 2001059 --database main

# For ArchiveRevokedAccessGrants
/chatops run batched_background_migrations status 2001064 --database main

References

Related to: #578650 (closed)
ArchiveRevokedAccessTokens BBM shipped in !197692 (merged)
ArchiveRevokedAccessGrants BBM shipped in !204337 (merged)
Main plan: #555382

Database


          
>>> Executing: bin/rails db:migrate:up:main VERSION=20251102091505
main: == [advisory_lock_connection] object_id: 130300, pg_backend_pid: 14917
main: == 20251102091505 FinalizeArchiveRevokedAccessGrants: migrating ===============
main: -- transaction_open?(nil)
main:    -> 0.0000s
main: == 20251102091505 FinalizeArchiveRevokedAccessGrants: migrated (0.0453s) ======

main: == [advisory_lock_connection] object_id: 130300, pg_backend_pid: 14917
>>> Executing: bin/rails db:migrate:up:ci VERSION=20251102091505
ci: == [advisory_lock_connection] object_id: 130300, pg_backend_pid: 14955
ci: == 20251102091505 FinalizeArchiveRevokedAccessGrants: 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_ci_cell_local, :gitlab_internal, :gitlab_shared, :gitlab_shared_cell_local, :gitlab_shared_org].
ci: == 20251102091505 FinalizeArchiveRevokedAccessGrants: migrated (0.0181s) ======

ci: == [advisory_lock_connection] object_id: 130300, pg_backend_pid: 14955

>>> Executing: bin/rails db:migrate:up:main VERSION=20251102091753
main: == [advisory_lock_connection] object_id: 130300, pg_backend_pid: 15045
main: == 20251102091753 FinalizeArchiveRevokedAccessTokens: migrating ===============
main: -- transaction_open?(nil)
main:    -> 0.0000s
main: == 20251102091753 FinalizeArchiveRevokedAccessTokens: migrated (0.0580s) ======

main: == [advisory_lock_connection] object_id: 130300, pg_backend_pid: 15045
>>> Executing: bin/rails db:migrate:up:ci VERSION=20251102091753
ci: == [advisory_lock_connection] object_id: 130300, pg_backend_pid: 15072
ci: == 20251102091753 FinalizeArchiveRevokedAccessTokens: 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_ci_cell_local, :gitlab_internal, :gitlab_shared, :gitlab_shared_cell_local, :gitlab_shared_org].
ci: == 20251102091753 FinalizeArchiveRevokedAccessTokens: migrated (0.0405s) ======

ci: == [advisory_lock_connection] object_id: 130300, pg_backend_pid: 15072

How to set up and validate locally

Run migrations

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.

Edited by Daniele Bracciani

Merge request reports