Skip to content

Batched migration for expires_at update for Personal Access Token

Smriti Garg requested to merge smriti-369123/migration_expires_at into master

What does this MR do and why?

For solving Issue - #369123 (closed)

There are two steps

  1. To make sure no new tokens are generated with nil value that MR is already in progress here !120213 (merged)
  2. To make sure no existing token has nil expiry date

Batched migration are for expires_at update

Update expires_at column value to 365 days from now when its nil

As per issue we cannot support PATs which do not expire ever. With this migration change we are making sure no such tokens are there in system with nil expiry date

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports