Thanks to a quick turn around by the mcohen01, the author, two bugs have
been fixed with the bucket notifications and tagging :) The project docs
(README) have been updated with examples.
On Friday, 22 July 2016 02:24:45 UTC+1, Andrea Richiardi wrote:
>
> I am glad you solved and raised the
I am glad you solved and raised the issue so that we can track that!
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with
I've created this issue https://github.com/mcohen01/amazonica/issues/230
for the set-bucket-notification-configuration as I believe there is a
problem with the use of that function.
Having looked at the trace out from set-bucket-notification-configuration I'm
convinced I can get
Thanks that's helpful. I must have been too frustrated by the end of the
day and didn't Google that one!
Reading the trace output for the tag setting I believe the original code I
wrote is producing an empty TagSet which is what the API considers
malformed. Looks like a element is required:
Maybe not related, but I was checking that api and this showed up, maybe it
can be helpful?
https://stackoverflow.com/questions/30521046/malformedxml-when-tagging-an-s3-bucket
On Wednesday, July 20, 2016 at 7:56:10 AM UTC-7, Gareth Rogers wrote:
>
> After chatting with a colleague who read this
After chatting with a colleague who read this and showed me the magic of
trace I think the problem with amazonica.aws.
s3/set-bucket-tagging-configuration is that I need
{:tag-sets [{:tag {"Formation" "notlive"}}]}
i.e. I need to know how to call setTag(string key, string value) which
takes
Hi
Has any one had any success using either
amazonica.aws.s3/set-bucket-notification-configuration or
amazonica.aws.s3/set-bucket-tagging-configuration?
I've got
(amazonica.aws.s3/set-bucket-notification-configuration
"my.bucket.name"
{"my-custom-event-name"
{"" ;; This replaced
