Add copilot data in level4 api, and cleanups #4840
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
It's no longer needed by airlock
Added some defaults, caught some minor issues.
This will allow us to list copiloted projects for a user
This existed, and had some test set up, but was not actually set. We're about to store user data in a persistant way in airlock, so it would be good to have this for that purpose.
Jongmassey
approved these changes
Feb 6, 2025
Yes, precisely. On log in, and every 15m whilst logged in, airlock will call this API, and update our user table with whatever it tells us. Our persistent storage is just a read-only cache, really. The main motivation here is to be able to show the full name of other users in airlock, rather than github username. See opensafely-core/airlock#443 for more |
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.
This adds copiloted workspace data, so we can use that in airlock.
It also cleans up a few small issues, and completes the implementation of the staff field.
Fixes #4837