You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2018/04/23 19:44:00 UTC

[jira] [Created] (DISPATCH-976) Allow policy for sources and targets to handle multiple wildcards

Chuck Rolke created DISPATCH-976:
------------------------------------

             Summary: Allow policy for sources and targets to handle multiple wildcards
                 Key: DISPATCH-976
                 URL: https://issues.apache.org/jira/browse/DISPATCH-976
             Project: Qpid Dispatch
          Issue Type: Bug
          Components: Policy Engine
    Affects Versions: 1.0.1
            Reporter: Chuck Rolke
            Assignee: Chuck Rolke


As per the [upstream policy documentation|https://github.com/apache/qpid-dispatch/blob/1.0.0/doc/book/policy.adoc] in the secion on [AMQP Source and Target Wildcard and Name Substitution|https://github.com/apache/qpid-dispatch/blob/1.0.0/doc/book/policy.adoc#amqp-source-and-target-wildcard-and-name-substitution] utilization of the asterisk wildcard is constrained as per the following quote:
{quote}The asterisk is recognized only if it is the last character in the link name.
{quote}
It is desirable that the configuration could handle a situation where there are multiple asterisks in use such as:

 
|{color:#000000}"tstGroup": {{color}|
|{color:#000000} "users": "tst@amq",{color}|
|{color:#000000} "sources": "abc.*,my.*.b2b.tst.*",{color}|
|{color:#000000} "targets": "abc.*,my.*.b2b.tst.*",{color}|
|{color:#000000} "remoteHosts": "*"{color}|
|{color:#000000}} {color}|

 
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org