Skip to content

Improvements to Access token resources

What does this MR do and why?

Describe in detail what your merge request does and why.

We are noticing Project and Group access token bot users pile up on Staging and Staging Ref although the delete-test-resources job logs show the access token resources are cleaned up (the bot users are also removed when the associated tokens are revoked).

This MR will help with debugging by uniquely setting the name of the access tokens and also printing the username of the associated bot user.

It also:

  • Fixes api_get_path of these resources which should include an id.
  • Ensures id and other attributes are populated when the resource is created on the browser by calling a reload!.
  • Fixes api_post_path for ImpersonationToken resource.
  • Sets default expires_at value for the token resources.

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.

Edited by Sanad Liaquat

Merge request reports

Loading