-
Notifications
You must be signed in to change notification settings - Fork 69
Implement Credential Caching #75
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.
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
Conversation
This introduces a socket based credential cache to allow caching of keys so that users do not need to go through the OIDC flow multiple times for batch operations (e.g. rebases). Credentials are keyed to git working directories so that different repos can cache different identities, and credentials are never directly stored to disk. Signed-off-by: Billy Lynch <billy@chainguard.dev>
Signed-off-by: Billy Lynch <billy@chainguard.dev>
Signed-off-by: Billy Lynch <billy@chainguard.dev>
Signed-off-by: Billy Lynch <billy@chainguard.dev>
Signed-off-by: Billy Lynch <billy@chainguard.dev>
Signed-off-by: Billy Lynch <billy@chainguard.dev>
Signed-off-by: Billy Lynch <billy@chainguard.dev>
Signed-off-by: Billy Lynch <billy@chainguard.dev>
Signed-off-by: Billy Lynch <billy@chainguard.dev>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Only blocking comment is about permissions of the socket
- Return CertSignerVerifier - Move static values to const - Use XDG_CACHE_DIR for user data directory. Signed-off-by: Billy Lynch <billy@chainguard.dev>
Signed-off-by: Billy Lynch <billy@chainguard.dev>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's do it!
When this goes in I'll try it out for a few days and see if anything breaks. 🤞
Summary
This introduces a socket based credential cache to allow caching of keys
so that users do not need to go through the OIDC flow multiple times
for batch operations (e.g. rebases).
Credentials are keyed to git working directories so that different repos can
cache different identities, and credentials are never directly stored to disk.
Signed-off-by: Billy Lynch billy@chainguard.dev
Ticket Link
Fixes #21
Release Note