Draft: Add trigger token expiration
What does this MR do and why?
Personal Access Tokens currently provide significantly more functionality than Pipeline Trigger Tokens. This MR is an initial step towards closing the inconsistency between token types by adding an optional expiration date to Pipeline Trigger Tokens.
There has been a significant amount of past discussion surrounding this topic, including the following issues and epics:
This MR is currently a draft, and is not intended to be final work.
As of now, I am looking for feedback on the overall approach. I think it would ultimately make sense to convert trigger tokens to a scope of personal access tokens, but it is not clear to me how feasible that is at this time. As a compromise, this MR adds support for pipeline trigger token expiration, without creating inconsistencies which would render merging them into regular personal access tokens impossible in the future.
Additionally, I would like to check on the status of any other similar work to see how this change fits into the project as a whole.
MR acceptance checklist
TODO
Screenshots or screen recordings
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
TODO