-
Notifications
You must be signed in to change notification settings - Fork 1.9k
remove claimed restriction about https proxy urls #25438
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
|
@wking i left |
|
the actual proxy config validation explicitly allows http+https: |
|
@openshift/team-documentation ptal |
|
Cc: @bergerhoffer for review. It looks like this was content added in #16635 for OCP 4.2. |
|
@bparees so are you saying that the text |
|
@danehans Can you confirm this as well? The request to add this note was here: #16635 (comment) |
I don't think it was ever restricted, even 4.2 tolerates both: |
|
@bergerhoffer I have no objections as long as https://issues.redhat.com/browse/BUILD-68 is completed. |
|
Got ack from @danehans that it's okay to remove this, as long as there is a note about the lack of git clone support when using an |
bergerhoffer
left a comment
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.
This LGTM
|
The https proxy works well for installer side. @wzheng1 could you please help to provide an ack on this? Considering it's the restriction on BUILD. |
|
LGTM, thanks! |
|
@bergerhoffer can we merge this? |
|
@bparees did I trip over this by accident? Or is this unrelated to https://bugzilla.redhat.com/show_bug.cgi?id=1845929? I don't want to collide if my PR is superseded by this. Thanks! |
unrelated. |
|
@bparees Sorry missed the notification. Merging! |
|
/cherrypick enterprise-4.6 |
|
/cherrypick enterprise-4.5 |
|
/cherrypick enterprise-4.4 |
|
@bergerhoffer: new pull request created: #26157 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick enterprise-4.3 |
|
@bergerhoffer: new pull request created: #26158 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@bergerhoffer: new pull request created: #26159 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@bergerhoffer: new pull request created: #26160 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
as far as i know this works (it's why we allow you to configure proxy CAs). https proxies do not work with builds for purposes of source retrieval, due to a limitation in the git version we use. That limitation will be going away in 4.6. It's possible that restriction is where this line came from, i'm not sure.
So maybe it's worth noting that restriction in the build docs explicitly, or we just let it go knowing that the problem is going away sooner than later anyway.