Consul
Consul Services Export
Command: consul services export
The services export
command exports a service from one admin partition
or cluster peer to another. This command can be used in lieu of creating or updating the corresponding
exported-services
configuration entry. Running the command multiple times with the same
arguments results in a no-op.
Usage: consul services export [options] -name <service name> -consumer-peers <other cluster name>
Export a service to a peered cluster.
$ consul services export -name=web -consumer-peers=other-cluster
Use the -consumer-partitions flag instead of -consumer-peers to export to a different partition in the same cluster.
$ consul services export -name=web -consumer-partitions=other-partition
Additional flags and more advanced use cases are detailed below.
Command options
-name=<string>
- (Required) The name of the service to export.-consumer-peers=<string>
- (Required) A comma-separated list of cluster peers to export the service to. In Consul Enterprise, this flag is optional when-consumer-partitions
is specified.
Enterprise options
-consumer-partitions=<string>
- A comma-separated list of admin partitions within the same datacenter to export the service to. This flag is optional when-consumer-peers
is specified.
-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 thedefault
partition.
-namespace=<string>
- Specifies the namespace to query. If not provided, the namespace will be inferred from the request's ACL token, or will default to thedefault
namespace. Namespaces are a Consul Enterprise feature added in v1.7.0.
API options
-ca-file=<value>
- Path to a CA file to use for TLS when communicating with Consul. This can also be specified via theCONSUL_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 theCONSUL_CAPATH
environment variable.-client-cert=<value>
- Path to a client cert file to use for TLS whenverify_incoming
is enabled. This can also be specified via theCONSUL_CLIENT_CERT
environment variable.-client-key=<value>
- Path to a client key file to use for TLS whenverify_incoming
is enabled. This can also be specified via theCONSUL_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 theCONSUL_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 variableCONSUL_HTTP_SSL=true
. This may be a unix domain socket usingunix:///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 theCONSUL_TLS_SERVER_NAME
environment variable.-token=<value>
- ACL token to use in the request. This can also be specified via theCONSUL_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 orCONSUL_HTTP_TOKEN
environment variable. This can also be specified via theCONSUL_HTTP_TOKEN_FILE
environment variable.
Examples
In the following example, the consul services export
command makes the web
service available to services running in a cluster named dc2
that has a previously-established cluster peering connection.
$ consul services export -name=web -consumer-peers=dc2
In the following example, the consul services export
command makes the web
service located in the
namespace ns1
and the admin partition alpha
to other admin partitions named beta
and delta
.
$ consul services export -name=web -namespace=ns1 -partition=alpha -consumer-partitions=beta,delta