Skip to content
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

Replace Consul SkipVerifyTLS handling #3983

Closed
wants to merge 1 commit into from

Commits on Mar 15, 2018

  1. 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.
    schmichael committed Mar 15, 2018
    Configuration menu
    Copy the full SHA
    9f50ab3 View commit details
    Browse the repository at this point in the history