From 5e4ec51a40a32cdbfae5912c70ade17870b411d8 Mon Sep 17 00:00:00 2001 From: Waldemar Quevedo Date: Wed, 11 Dec 2019 21:09:50 +0100 Subject: [PATCH] Apply suggestions from code review --- developing-with-nats/receiving/queues.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/developing-with-nats/receiving/queues.md b/developing-with-nats/receiving/queues.md index 061e820..b529e77 100644 --- a/developing-with-nats/receiving/queues.md +++ b/developing-with-nats/receiving/queues.md @@ -127,6 +127,10 @@ If you run this example with the publish examples that send to `updates`, you wi Added in NATS Server v2.1.2, Queue Permissions allow you to express authorization for queue groups. As queue groups are integral to implementing horizontally scalable microservices, control of who is allowed to join a specific queue group is important to the overall security model. +A Queue Permission can be defined with the syntax ` `, where the name of the queue can also use wildcards, for example the following would allow clients to join queue groups v1 and v2.*, but won't allow plain subscriptions: + +```hcl +allow = ["foo v1", "foo v2.*"] ```text users = [ { @@ -143,4 +147,3 @@ users = [ allow: [“foo”, “foo v1”] ``` -