-
Notifications
You must be signed in to change notification settings - Fork 50
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
Feature request: add option for skipping SSL verification when using Git #260
Comments
Thanks for submitting this issue @alexandreroman , would you be interesting in making a PR with the change? |
I'm not into Go, but I'm happy to help with testing when you get something ready. |
Response from @alexandreroman - As per above message seems like we need to implement this in kapp-controller. |
Correct: from a user perspective, kapp-controller will have to configure vendir to skip TLS verification (this is my use case). Reusing the existing flag |
@alexandreroman - Here is the PR (#265) for adding option for skipping SSL verification when using Git. I have merged this PR to develop. This feature should be available with the next release of vendir. |
Fixed in release v0.36.0 |
Describe the problem/challenge you have
vendir has no option for setting
GIT_SSL_NO_VERIFY=true
, which could be used with Git repos using a self-signed certificate.This environment variable tells Git not to verify SSL certificates.
Describe the solution you'd like
The current implementation already sets a few environment variables when using Git, such as
GIT_LFS_SKIP_SMUDGE=1
to skip downloading lfs files.I wish there was a way to disable SSL verification when using Git, by adding a flag in the Git configuration.
For example:
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
The text was updated successfully, but these errors were encountered: