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.

Sign up for GitHub

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

Jump to bottom

Add support for TLS configuration in NSQ input to reach HTTPS nsqd endpoints #3903

Merged
merged 4 commits into from
Oct 23, 2018
Merged

Add support for TLS configuration in NSQ input to reach HTTPS nsqd endpoints #3903

merged 4 commits into from
Oct 23, 2018

Commits on Oct 16, 2018

  1. Add support for TLS configuration in NSQ input to reach HTTPS nsqd en… 

    …dpoints

Goal: A completely secure NSQ doesn't have any HTTP endpoint, but only
HTTPS, often with x509 client authentication. This PR aims at
configuring the HTTP client to correctly connects to nsqd

Choices: TLS configuration build is only done once, and the first
`Gather()` will return an error, if configuration is invalid, then it
will be silent. The HTTP client is only built once, to limit allocations
    @Soulou
    Soulou committed Oct 16, 2018
    Configuration menu
    Copy the full SHA
    1cbf1e4 View commit details
    Browse the repository at this point in the history

  2. Update nsq inputs tests

    @Soulou
    Soulou committed Oct 16, 2018
    Configuration menu
    Copy the full SHA
    aace5d8 View commit details
    Browse the repository at this point in the history

  3. Finally correctly configure TLS configuration for nsq input

    @Soulou
    Soulou committed Oct 16, 2018
    Configuration menu
    Copy the full SHA
    8b0f188 View commit details
    Browse the repository at this point in the history

  4. nsq input: update example config

    @Soulou
    Soulou committed Oct 16, 2018
    Configuration menu
    Copy the full SHA
    e7a6fd4 View commit details
    Browse the repository at this point in the history