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

website: clarify that modifying intentions will not kill the conn

This commit is contained in:
Mitchell Hashimoto 2018-06-16 20:12:29 -07:00 committed by Jack Pearkes
parent 7a1031fdc5
commit 79778635e8
2 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
website/source/docs/connect/intentions.html.md
View File

@ -44,6 +44,11 @@ The intention above is a deny intention with a source of "web" and
destination of "db". This says that connections from web to db are not
allowed and the connection will be rejected.
When an intention is modified, existing connections will not be affected.
This means that changing a connection from "allow" to "deny" today
_will not_ kill the connection. Addressing this shortcoming is on
the near term roadmap for Consul.
### Wildcard Intentions
An intention source or destination may also be the special wildcard

5
website/source/intro/getting-started/connect.html.md
View File

@ -185,6 +185,11 @@ connection again. Intentions allow services to be segmented via a centralized
control plane (Consul). To learn more, read the reference documentation on
[intentions](/docs/connect/intentions.html).
Note that in the current release of Consul, changing intentions will not
affect existing connections. Therefore, you must establish a new connection
to see the effects of a changed intention. This will be addressed in the near
term in a future version of Consul.
## Next Steps
We've now configured a service on a single agent and used Connect for