Make source/destination cloud insecure connection configurable#240
Merged
Conversation
matbu
approved these changes
May 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OpenStack and VMware client had no SSL/TLS validation by default. With this PR:
TLS certificate verification is now enabled by default for both OpenStack and VMware connections
Flexible for non-production environments: Lab, development, and testing environments can opt-in to insecure connections using dedicated parameters:
vmware_insecure: Set to true to disable certificate verification for VMware/ESXi connectionsopenstack_insecure: Set to true to disable certificate verification for OpenStack API connectionsAudit logging: When insecure connections are enabled, warnings are logged for visibility and compliance tracking