-
Notifications
You must be signed in to change notification settings - Fork 120
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
Set insecure_connection to target provider as default behavior. #327
Set insecure_connection to target provider as default behavior. #327
Conversation
Checked commit fabiendupont@9e9248d with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
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.
if possible can we pick up the secure connection from the method instance as a default value. Or put a TODO in this file to indicate that we want it to be configurable
@mkanoor It would mean changing the class schema. And this adds more complexity. Anyway, you're right it has to be configurable. I was going to create an issue to track the v2v configuration topic as it is broader than certificates validation. But we don't know yet what component will be targeted to store configuration. |
@fdupont-redhat Its your choice, I am ok with just updating the method with a Git Issue pointing to that line in the method to make it configurable |
@mkanoor |
…s_default Set insecure_connection to target provider as default behavior. (cherry picked from commit cd8a56f)
Gaprindashvili backport details:
|
During tests of V2V solution, we identified that it is highly probable that the certificate presented by RHV-M is not valid. virt-v2v-wrapper has an option to work in insecure mode and this PR makes it the default behavior to avoid transformation to fail due to an invalid certificate.