HashiConf 2024 Now streaming live from Boston! Attend for free
Consul
Consul Home

You are viewing documentation for version v1.19.x. View latest version.

Consul Intention Create

Deprecated - This command is deprecated in Consul 1.9.0 in favor of using the config entry CLI command. To create an intention, create or modify a service-intentions config entry for the destination.

Command: consul intention create

Corresponding HTTP API Endpoint: [POST] /v1/connect/intentions

The intention create command creates or updates an L4 intention.

The table below shows this command's required ACLs. Configuration of blocking queries and agent caching are not supported from commands, but may be from the corresponding HTTP endpoint.

ACL Required
intentions:write

Define intention rules in the service policy. Refer to ACL requirements for intentions for additional information.

Usage

SRC and DST can both take several forms.

Command Options

  • -allow - Set the action to "allow" for intentions. This is the default.

  • -deny - Set the action to "deny" for intentions. This cannot be specified with -allow.

  • -file - Read intention data one or more files specified by the command line arguments, instead of source/destination pairs.

  • -meta key=value - Specify arbitrary KV metadata to associate with the intention.

  • -replace - Replace any matching intention. The replacement is done atomically per intention.

Enterprise Options

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

Create an intention web => db:

$ consul intention create web db

Create intentions from a set of files:

$ consul intention create -file one.json two.json

Create intentions from a directory using shell expansion:

$ consul intention create -file intentions/*.json