Add last used column for API tokens #12114
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #11870
Occurred changes and/or fixed issues
The PR adds the 'Last Used' information for API tokens, as implemented by this backend PR: rancher/rancher#45732
Technical notes summary
Fairly simple - we define a new column and add it to the API Keys/Tokens table. Added translation as well.
Note: This PR has been updated following review to show
Unknown
for the case that information is not available, since we can not determine been a token that has not been used and one that was created before this feature was updated, which may have been used.Areas or cases that should be tested
Screenshot/Video
New 'Last Used' column:
Hover on last used shows absolute date/time:
Checklist