Browse Source

Fix consul connect token env variable doc (#5942)

The cli documentation for consul connect commands incorrectly indicated
to use CONSUL_TOKEN instead of CONSUL_HTTP_TOKEN env var.
pull/6885/head
Aestek 5 years ago committed by Chris Piraino
parent
commit
6817676223
  1. 2
      command/connect/envoy/envoy.go
  2. 2
      command/connect/proxy/proxy.go

2
command/connect/envoy/envoy.go

@ -594,7 +594,7 @@ Usage: consul connect envoy [options]
arguments using -bootstrap.
The proxy requires service:write permissions for the service it represents.
The token may be passed via the CLI or the CONSUL_TOKEN environment
The token may be passed via the CLI or the CONSUL_HTTP_TOKEN environment
variable.
The example below shows how to start a local proxy as a sidecar to a "web"

2
command/connect/proxy/proxy.go

@ -405,7 +405,7 @@ Usage: consul connect proxy [options]
a non-Connect-aware application to use Connect.
The proxy requires service:write permissions for the service it represents.
The token may be passed via the CLI or the CONSUL_TOKEN environment
The token may be passed via the CLI or the CONSUL_HTTP_TOKEN environment
variable.
Consul can automatically start and manage this proxy by specifying the

Loading…
Cancel
Save