open-consul/website/content/commands/intention/create.mdx
Luke Kysow 4217488e78
Move cfg entry docs to under connect from agent (#9533)
Since all config entries are currently related to service mesh it's a
much more natural place to look for them under Service Mesh than under
Agent.
2021-01-13 12:48:48 -08:00

69 lines
1.7 KiB
Plaintext

---
layout: commands
page_title: 'Commands: Intention Create'
sidebar_title: create
---
# Consul Intention Create
-> **Deprecated** - This command is deprecated in Consul 1.9.0 in favor of
using the [config entry CLI command](/commands/config/write). To create an
intention, create or modify a
[`service-intentions`](/docs/connect/config-entries/service-intentions) config
entry for the destination.
Command: `consul intention create`
The `intention create` command creates or updates an L4 intention.
## Usage
- `consul intention create [options] SRC DST`
- `consul intention create [options] -file FILE...`
`SRC` and `DST` can both take [several forms](/commands/intention#source-and-destination-naming).
#### API Options
@include 'http_api_options_client.mdx'
#### Enterprise Options
@include 'http_api_namespace_options.mdx'
#### Intention Create 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.
## Examples
Create an intention `web => db`:
```shell-session
$ consul intention create web db
```
Create intentions from a set of files:
```shell-session
$ consul intention create -file one.json two.json
```
Create intentions from a directory using shell expansion:
```shell-session
$ consul intention create -file intentions/*.json
```