Draft: Populate job token authorizations for projects with disabled scope
What does this MR do and why?
Related to Populate authentications list if job token scop... (#467292)
Database migrations
$ rails db:migrate
main: == [advisory_lock_connection] object_id: 127700, pg_backend_pid: 90001
main: == 20240813191915 CreateCiJobTokenAuthorizations: migrating ===================
main: -- create_table(:ci_job_token_authorizations, {:if_not_exists=>true})
main: -> 0.0227s
main: == 20240813191915 CreateCiJobTokenAuthorizations: migrated (0.0422s) ==========
main: == [advisory_lock_connection] object_id: 127700, pg_backend_pid: 90001
ci: == [advisory_lock_connection] object_id: 127960, pg_backend_pid: 90007
ci: == 20240813191915 CreateCiJobTokenAuthorizations: migrating ===================
ci: -- create_table(:ci_job_token_authorizations, {:if_not_exists=>true})
ci: -> 0.0033s
ci: == 20240813191915 CreateCiJobTokenAuthorizations: migrated (0.0283s) ==========
ci: == [advisory_lock_connection] object_id: 127960, pg_backend_pid: 90007
$ rails db:migrate:redo:ci VERSION=20240813191915
ci: == [advisory_lock_connection] object_id: 127000, pg_backend_pid: 96766
ci: == 20240813191915 CreateCiJobTokenAuthorizations: reverting ===================
ci: -- drop_table(:ci_job_token_authorizations, {:if_not_exists=>true})
ci: -> 0.0116s
ci: == 20240813191915 CreateCiJobTokenAuthorizations: reverted (0.0406s) ==========
ci: == [advisory_lock_connection] object_id: 127000, pg_backend_pid: 96766
ci: == [advisory_lock_connection] object_id: 127980, pg_backend_pid: 97095
ci: == 20240813191915 CreateCiJobTokenAuthorizations: migrating ===================
ci: -- create_table(:ci_job_token_authorizations, {:if_not_exists=>true})
ci: -> 0.0265s
ci: == 20240813191915 CreateCiJobTokenAuthorizations: migrated (0.0846s) ==========
ci: == [advisory_lock_connection] object_id: 127980, pg_backend_pid: 97095
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Edited by Fabio Pitino