-
Notifications
You must be signed in to change notification settings - Fork 619
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
Add create secret git
with bearer token
#3536
Comments
create secret git
with bearer token
I can try this |
hey can you explain what exactly is to be done I am confused. |
hey, we need to modify the |
Hey @aryan9600, I was looking at this and wanted to confirm, after the implementation the correct command for creating a git secret with a token while
|
@Santosh1176 that seems right. @patel-aum are you still working on it? Do you need any help? |
Thank you @darkowlzz. I've made some changes to === RUN TestCreateGitSecret/ssh_key_with_password
=== RUN TestCreateGitSecret/https_with_bearer_token
main_test.go:352: Mismatch from golden file 'testdata/create_secret/git/git-token-secret.yaml': Mismatch from expected value (-want +got):
(
"""
... // 4 identical lines
name: podinfo-auth
namespace: frontend-api
- data:
- bearerToken: ghp_vaB2qnFE0O41WlucePL3udt2N9vVZK4R0hSN I think the error is for not able to generate the |
I have unassign myself as @Santosh1176 has demonstrated a clear understanding of the problem, while I am still in the process of figuring it out. |
@patel-aum thanks. @Santosh1176 It may be that the content of the golden file you created doesn't match with the actual output, maybe due to some white spaces or tabs. It'd be easier if you could share the code in a pull request and we can have a look. |
Support for using bearer token for git authentication was added in fluxcd/pkg#442.
flux create secret git
command supports creating Secret for basic auth and ssh authentication. Add support for creating a Secret with bearer token.Refer GitRepository docs for an example of the Secret to be created.
The text was updated successfully, but these errors were encountered: