Remove retain_resource_access_token_user_after_revoke FF
What does this MR do and why?
We enabled retain_resource_access_token_user_after_revoke FF on GitLab.com and confirmed that implementation that is behind it works as expected, see #468606 (comment 2286735362).
This MR removes this FF from the application to release this feature for GitLab self-managed in %17.9.
Related MRs:
- Retain resource access token bot users after re... (!157130 - merged)
- Display inactive resource access tokens when fe... (!157254 - merged)
- Create bot users with indefinite group and proj... (!158291 - merged)
- Update inactive token docs (!165663 - merged)
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
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.