-
Notifications
You must be signed in to change notification settings - Fork 60
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
feat: kurtosis github login #2113
Conversation
️✅ There are no secrets present in this pull request anymore.If these secrets were true positive and are still valid, we highly recommend you to revoke them. 🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request. |
...ngine-lib/lib/backend_impls/docker/docker_kurtosis_backend/engine_functions/create_engine.go
Show resolved
Hide resolved
container-engine-lib/lib/backend_impls/docker/docker_kurtosis_backend/consts/consts.go
Show resolved
Hide resolved
🤖 I have created a release *beep* *boop* --- ## [0.86.16](0.86.15...0.86.16) (2024-02-07) ### Features * kurtosis github login ([#2113](#2113)) ([2f0d638](2f0d638)) ### Bug Fixes * Remove Derek and Karla as default assignees for docs issues ([#2129](#2129)) ([2f1eecc](2f1eecc)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: kurtosisbot <[email protected]>
Description:
This change enables GitHub users over Docker to authorize with Kurtosis CLI so that Kurtosis can perform git operations such as cloning packages in private repositories. This primarily enables the use of private GitHub locators for package runs,
import_module
, andupload_files
.This is accomplished via an OAuth flow where
kurtosis github login
directs the user to authorize Kurtosis CLI to take actions on their behalf. A token is retrieved upon success and is used by Kurtosis for subsequent git operations. Kurtosis attempts to store the token in secure system storage, but if not found, the token is stored in a plain text file atkurtosis config path
.Github commands added:
kurtosis github login
kurtosis github logout
kurtosis github token
kurtosis github status
Flags added (these override existing GitHub login for one off authorization use cases):
kurtosis engine start --github-auth-token=< token.txt
kurtosis engine restart --github-auth-token=< token.txt
Is this change user facing?
YES
References:
#2020