News HashiCorp to join IBM to accelerate multi-cloud automation. Read the blog →
Consul
Consul Home

Consul Peering Read

Command: consul peering read

Corresponding HTTP API Endpoint: [GET] /v1/peering/:name

The peering read displays information on the status of a peering connection.

The table below shows this command's required ACLs.

ACL Required
peering:read

Usage

Usage: consul peering read [options] -name <peer name>

Command Options

  • -name=<string> - (Required) The name of the peer associated with a connection that you want to read.

  • -format={pretty|json} - Command output format. The default value is pretty.

Enterprise Options

  • -partition=<string> - Enterprise Specifies the admin partition to query. If not provided, the partition is inferred from the request's ACL token, or defaults to the default partition.

API Options

  • -ca-file=<value> - Path to a CA file to use for TLS when communicating with Consul. This can also be specified via the CONSUL_CACERT environment variable.

  • -ca-path=<value> - Path to a directory of CA certificates to use for TLS when communicating with Consul. This can also be specified via the CONSUL_CAPATH environment variable.

  • -client-cert=<value> - Path to a client cert file to use for TLS when verify_incoming is enabled. This can also be specified via the CONSUL_CLIENT_CERT environment variable.

  • -client-key=<value> - Path to a client key file to use for TLS when verify_incoming is enabled. This can also be specified via the CONSUL_CLIENT_KEY environment variable.

  • -http-addr=<addr> - Address of the Consul agent with the port. This can be an IP address or DNS address, but it must include the port. This can also be specified via the CONSUL_HTTP_ADDR environment variable. In Consul 0.8 and later, the default value is http://127.0.0.1:8500, and https can optionally be used instead. The scheme can also be set to HTTPS by setting the environment variable CONSUL_HTTP_SSL=true. This may be a unix domain socket using unix:///path/to/socket if the agent is configured to listen that way.

  • -tls-server-name=<value> - The server name to use as the SNI host when connecting via TLS. This can also be specified via the CONSUL_TLS_SERVER_NAME environment variable.

  • -token=<value> - ACL token to use in the request. This can also be specified via the CONSUL_HTTP_TOKEN environment variable. If unspecified, the query will default to the token of the Consul agent at the HTTP address.

  • -token-file=<value> - File containing the ACL token to use in the request instead of one specified via the -token argument or CONSUL_HTTP_TOKEN environment variable. This can also be specified via the CONSUL_HTTP_TOKEN_FILE environment variable.

Examples

The following example outputs information about a peering connection locally referred to as "cluster-02":

$ consul peering read -name cluster-02Name:         cluster-02ID:           3b001063-8079-b1a6-764c-738af5a39a97State:        ACTIVEMeta:    env=production Peer ID:               e83a315c-027e-bcb1-7c0c-a46650904a05Peer Server Name:      server.dc1.consulPeer CA Pems:          0Peer Server Addresses:    10.0.0.1:8300 Imported Services: 0Exported Services: 2 Create Index: 89Modify Index: 89
Edit this page on GitHub