Repository navigation
feat(svo-adapter): a user stores, lists and deletes their own secrets - #449
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Step 1 of the design for a runner's own secrets. Nothing uses a stored secret
yet.
- PUT /secrets/{name}, GET /secrets, DELETE /secrets/{name}, with the caller's
own Tapis token. No route returns a value.
- A secret cannot be changed while its owner has a run in progress, because a
step of that run holds the same token.
- At most 20 changes per user in ten minutes. Every change is recorded with
who made it.
- A model owner's secret must name a configuration, so it can never read as a
user's secret. A test fails if any role is granted access to the secret
tables or to a run's bound secrets.
wmobley
force-pushed
the
feat/user-secrets-store
branch
from
November 20, 2026 02:53
48e667a to
41a61da
Compare
This was referenced Nov 20, 2026
This branch was successfully deployed
This file contains hidden or 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
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.
Step 1 of the design in #440. Nothing uses a stored secret yet.
PUT /secrets/{name},GET /secrets,DELETE /secrets/{name}, with the caller's own Tapis token. No route returns a value; a refused body is not echoed.No table change:
adapter.secretalready allowed the user scope.Known limits: the lock and the rate limit are per process, and the lock check and the write are not one step.
Tests: adapter 830 passing with the four failures that predate this work.