status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

added line about wildcard intentions not supported for admin partitions

This commit is contained in:
trujillo-adam 2022-01-03 15:31:58 -08:00
parent 6bef2b2eb4
commit 8852810eb5
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/content/docs/connect/intentions.mdx
View File

@ -94,11 +94,11 @@ accepted.
### Wildcard Intentions
You can use the `*` wildcard when defining an intention source or destination. The wildcard matches _any_ value and can serve as a "catch-all" entry for intentions that should have a wide scope.
You can use the `*` wildcard to match service names when defining an intention source or destination. The wildcard matches _any_ value, which enables you to set a wide initial scope when configuring intentions.
You can use a wildcard to match service names. If you are using Consul Enterprise, you can also use a wildcard to match a namespace.
The wildcard is supported in Consul Enterprise `namespace` fields (see [Namespaces](/docs/enterprise/namespaces) for additional information), but it _is not supported_ in `partition` fields (see [Admin Partitions](/docs/enterprise/admin-partitions) for additional information).
This example says that the "web" service cannot connect to _any_ service:
In the following example, the `web` service cannot connect to _any_ service:
```hcl
Kind = "service-intentions"
@ -111,7 +111,7 @@ Sources = [
]
```
And this example says that _no_ service can connect to the "db" service:
The `db` service is configured to deny all connection in the following example:
```hcl
Kind = "service-intentions"
@ -124,8 +124,8 @@ Sources = [
]
```
<EnterpriseAlert inline /> This example grants Prometheus
access to any service in any namespace.
<EnterpriseAlert inline /> This example grants Prometheus access to any service in
any namespace.
```hcl
Kind = "service-intentions"