The nomad-acl-token is being logged at the default logging level of info. I think that it makes sense to log other useful info at info level, but secret info like tokens would ideally never be logged, or at best, at debug level only.
In looking at the code, it seems most if not all logging is done at the info level, so other levels of logging aren't very useful as a work-around.

That

We should add some linting to the pipeline to help us catch issues with the code.

golangci-lint seems like a good choice, but I'm interested to hear if there are any other preferences before implementing this.

Description

Consul DNS Service is not available outside the container

Steps to reproduce the issue:

1. docker run -d -p 8600:8600 -p 8600:8600/udp --name consul bitnami/consul:latest
2. dig @127.0.0.1 -p 8600 consul.service.consul
3. Dig on container's ip is same result

Describe the results you received:

dig @127.0.0.1 -p 8600 consul.service.consul

; <<>> 

Consul

SHA256 checksums for Consul 1.0.6
verify the checksums signature file
HashiCorp's GPG key

Nomad

[SHA256 checksums for Nomad 0.7.1 ](https://releases.hashicorp.com/nomad/0.7.1/nomad_0.7

When trying to deploy I get the following error. Obviously I'm missing the API address... But what should I set it to?

$ docker-compose up
WARNING: The Docker Engine you're using is running in swarm mode.

Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.

To deploy your application across the swarm, 

The Consul instance group does not use a health check to verify the health of the instances, nor is the load balancer aware of the health of the instances.

Currently the Network load balancer is in use, which only permits legacy HTTP health checks. The global load balancer / TCP Proxy should be brought in instead, so that more pertinent health checks can be used.