Closed michaelkoetter closed 3 years ago
@michaelkoetter appreciate the feedback. I think this should be configured through an environment variable or the provider configuration (provider.tf) since terraform launches the provider and so there isn't an opportunity to pass an "insecure" flag.
Maybe something like this?
# Configure the XenServer Provider
provider "xenorchestra" {
# Must be ws or wss
url = "ws://hostname-of-server" # Or set XOA_URL environment variable
username = "<username>" # Or set XOA_USER environment variable
password = "<password>" # Or set XOA_PASSWORD environment variable
insecure = <true|false> # or set XOA_INSECURE
}
yep, would that work for your use case?
yes that would be perfect :)
This will be released in v0.12.0
I'm running XO from the sources with a self-signed certificate. This leads to the following error:
I know I could probably add the self-signed CA to some system store to make it work ... :smiley: But it would be much easier to have an "insecure" flag like most other TLS tools, which would basically skip certificate validation.