-
Notifications
You must be signed in to change notification settings - Fork 113
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
Does shipwright support access to Github with token? #968
Comments
Hi @wanjunlei, thank you for the feedback. I think you would create a basic-auth kubernetes secret like you did before with username and password, and you now take the personal access token as password. But, something we have not yet tested. But, also something that we should get into our documentation given this is a common scenario. If you can try with the personal access token as password and give us feedback if it works, that would be nice. |
I believe this is the correct answer - we have documentation in the build repository on how to do this: https://github.com/shipwright-io/build/blob/main/docs/development/authentication.md#basic-authentication |
/assign @adambkaplan |
Thanks for your replies, I will try this. |
From grooming: we will enhance the documentation to mention that repositories move away from password support towards token support instead, and link to the token documentation of the popular providers (GitHub, GitLab). |
I am using shipwright v0.7.0 to build Github's private repository. I created a secret containing
username
andpassword
, and then thestep-source-default
reported the following error:Then I create a secret include
token
, thestep-source-default
reported the following error:Does shipwright support access to Github with tokens? How should I configure the secret?
The text was updated successfully, but these errors were encountered: