Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
MIME-Version: 1.0
In-Reply-To: <570645AC.2020206@saticed.me.uk>
References: <570645AC.2020206@saticed.me.uk>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Thu, 7 Apr 2016 13:39:30 +0200
Message-ID: 
 <CAGB5yNk5CJ+UmKoEqDPAgB93xtTEk4G54Jc1j=NRwVhNRK_1Gg@mail.gmail.com>
Subject: Re: feedback on proposed arn for aws-sqs implementation
To: dev <dev@camel.apache.org>
Content-Type: text/plain; charset=UTF-8

Can you provide an example of the two uris with and withour arn. What
are the rules for an arn, is it just a text or does it use colons in
the text ?

The concern is how parsing the uri becomes more complicated in terms
of mapping that correct to the options.


On Thu, Apr 7, 2016 at 1:34 PM, Tristan Hill <tristan@saticed.me.uk> wrote:
> Hi,
> To simplify our application configuration I would like camel's aws-sqs
> component to accept an arn as well as the queue name is does currently.
> Since the region and account number are also in the arn this would also help
> avoid needing the listqueues permissions as the queue url could be
> constructed similar to the current implementation when region and account id
> are passed through.
>
> The format I am thinking of would be something like
> aws-sqs://arn:aws:sqs:eu-west-1:account_no:queue_name[?options], so
> overloading the current queue name parameter.  The implementation could then
> assume a name starting with arn: is actually an arn, otherwise a queue name
> as before.  Would this seem like a reasonable potential modification?
>
> Thanks
> Tristan


-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2