Update last used timestamp on ssh keys when used #457
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Avoid redundant whitespace.
smlx
changed the title
smlx
changed the title
smlx
force-pushed
the
last-used
branch
2 times, most recently
from
3edfcad
to
b83eeae
Compare
Update the last_used timestamp to the current time whenever an SSH key is used to either generate a token or query exec permissions on a Lagoon environment. The timestamp is updated every time the key is used, regardless of whether or not the permission check or token generation succeeds. Timestamps are converted and stored in UTC.
shreddedbacon
approved these changes
Jul 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Update the
last_usedattribute of ssh keys using the same technique as uselagoon/lagoon#3675:DATETIMEcolumn type.