Consul Support for HTTPS Addresses and Token

[bluk]

I've set the consul.address for service discovery, but it seems that HTTPS scheme is not supported for Consul connections.

  "client": {
    "enabled": true,
    "servers": [ "192.168.1.100" ],
    "options": {
      "consul.address": "192.168.1.100:8501"
    }
  },

Startup logs have something like:

2015/11/22 16:16:30 [ERROR] consul: Error while registering service ServiceName with Consul: Put http://192.168.1.100:8501/v1/agent/service/register: malformed HTTP response "\x15\x03\x01\x00\x02\x02"

I imagine that Consul token support is also necessary at some point.

[diptanu]

@bluk We are using the Consul api client, I think it uses http by default. Let me see how we can do https with it.

[diptanu]

@bluk Looks like the API client supports https via the Scheme parameter https://github.com/hashicorp/consul/blob/master/api/api.go#L157

We will add an option to support http very soon in the consul config, and until then if you set up the environment variables CONSUL_HTTP_SSL and CONSUL_HTTP_SSL_VERIFY via the Jobs DSL the current code should be able to do https since it appears that the client is reading those environment variables.

[bluk]

@diptanu Thanks!

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.