-
Notifications
You must be signed in to change notification settings - Fork 99
THREESCALE-7836 Exposed new env var to set porta client insecureSkipVerify flag #856
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
Hi @carlkyrillos. Thanks for your PR. I'm waiting for a 3scale member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Code Climate has analyzed commit 504d898 and detected 1 issue on this pull request. Here's the issue category breakdown:
View more on Code Climate. |
@carlkyrillos , it looks good to me. |
/lgtm |
/ok-to-test |
/lgtm |
There was a problem hiding this comment.
Choose a reason fo 8000 r hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
@carlkyrillos can you add documentation as well please |
@MStokluska I created a followup PR to add documentation |
Issue link
THREESCALE-7836
What
Refactors the PortaClient to default the TLS InsecureSkipVerify flag to false and exposes a new environment variable,
INSECURE_SKIP_VERIFY_CLIENT
that if1
will set the InsecureSkipVerify to true.Verification steps
ClusterServiceVersion
:ClusterServiceVersion
again, this time setting the environment variable to0
: