From 4d4a0b09e61061d6150146fd7a579e3dfdc0faea Mon Sep 17 00:00:00 2001 From: Matt Keeler Date: Wed, 4 Dec 2019 15:56:47 -0500 Subject: [PATCH] Trying out a different enterprise callout --- website/source/docs/acl/acl-rules.html.md.erb | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/website/source/docs/acl/acl-rules.html.md.erb b/website/source/docs/acl/acl-rules.html.md.erb index dcb0faafb121..3645e249bbce 100644 --- a/website/source/docs/acl/acl-rules.html.md.erb +++ b/website/source/docs/acl/acl-rules.html.md.erb @@ -562,12 +562,10 @@ Session rules are segmented by the node name they apply to. In the example above access to sessions on node name with the empty prefix, allow creating sessions on the node named "app", and deny all access to any sessions on the "admin" node. -#### Namespace Rules - -<%= enterprise_alert :consul %> +#### Namespace Rules Enterprise [Consul Enterprise](https://www.hashicorp.com/consul.html) 1.7.0 adds support for namespacing of many -Consul resources. ACL rules themselves can then be defined within a namespace and will only be applicable within that namespace. +Consul resources. ACL rules themselves can then be defined to only to apply to apply to specific namespaces. A Namespace specific rule would look like this: