Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

refactor: use api to store last accessed for user #3761

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

refactor: use api to store last accessed for user #3761

wants to merge 1 commit into from

Conversation

shreddedbacon
Copy link
Member

General Checklist

  • Affected Issues have been mentioned in the Closing issues section
  • Documentation has been written/updated
  • PR title is ready for inclusion in changelog

Database Migrations

  • If your PR contains a database migation, it MUST be the latest in date order alphabetically

Repeated calls to the API can result in users getting duplicated last_accessed attributes added. This refactors to use the api-db instead with a insert or update on a new user table. Also reduces the extra calls to keycloak this previously did.

@shreddedbacon shreddedbacon modified the milestone: 2.20.0 Jul 3, 2024
@shreddedbacon shreddedbacon mentioned this pull request Jul 3, 2024
Merged
4 tasks
@shreddedbacon shreddedbacon added the happy-to-delay pullrequest is fine to be left out of a release if required label Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
happy-to-delay pullrequest is fine to be left out of a release if required
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@shreddedbacon