Replace Consul TLSSkipVerify handling
Instead of checking Consul's version on startup to see if it supports TLSSkipVerify, assume that it does and only log in the job service handler if we discover Consul does not support TLSSkipVerify. The old code would break TLSSkipVerify support if Nomad started before Consul (such as on system boot) as TLSSkipVerify would default to false if Consul wasn't running. Since TLSSkipVerify has been supported since Consul 0.7.2, it's safe to relax our handling.
Showing
+274 -241
command/agent/consul/version_checker.go
0 → 100644
command/agent/consul/version_checker_test.go
0 → 100644
Please register or sign in to comment