Open theronic opened 7 years ago
Thanks for the report @pate β any chance you can give more context?
Also it may be worth to check what version of Amazonica is on the classpath. Since eu-west-2
is relatively new it might make sense to check with the most recent version of Amazonica/AWS Java libraries.
Version 0.1.5 can't publish to S3 buckets in eu-west2 region.
What kind of context do you need? Which library version do I need to bump to get the latest regions?
boot show -d
would be a good start. That said boot's pods should have eliminated any potential for a dependency conflict like this.
The task invocation leading up to this error would be helpful too. I'll create a bucket in eu-west-2
and try to reproduce once I know what exactly you're doing :)
This is still an issue, but I doubt it's a dependency conflict. Seems like an AWS dependency doesn't know about the (relatively new) EU (London) region?
β― boot show -d [21:16:41]
[adzerk/boot-reload "0.4.13" :scope "test"]
[clj-time "0.13.0"]
βββ [joda-time "2.9.7"]
[confetti "0.2.0"]
[deraen/boot-livereload "0.2.0"]
[hashobject/boot-s3 "0.1.2-20150920.195517-2"]
βββ [clj-aws-s3 "0.3.10"]
β βββ [com.amazonaws/aws-java-sdk "1.7.5"]
β βββ [com.fasterxml.jackson.core/jackson-annotations "2.1.1"]
β βββ [com.fasterxml.jackson.core/jackson-core "2.1.1"]
β βββ [com.fasterxml.jackson.core/jackson-databind "2.1.1"]
β βββ [commons-codec "1.3"]
β βββ [commons-logging "1.1.1"]
β βββ [org.apache.httpcomponents/httpclient "4.2"]
β βββ [org.apache.httpcomponents/httpcore "4.2"]
βββ [pandect "0.5.2"]
βββ [org.bouncycastle/bcprov-jdk15on "1.51" :exclusions [[org.clojure/clojure]]]
βββ [potemkin "0.3.11" :exclusions [[org.clojure/clojure]]]
βββ [clj-tuple "0.1.7"]
βββ [riddley "0.1.7"]
[hiccup "1.0.5"]
[jeluard/boot-notify "0.2.1" :scope "test"]
[org.clojure/clojure "1.8.0" :scope "provided"]
[org.clojure/tools.nrepl "0.2.12"]
[pandeiro/boot-http "0.7.6"]
[perun "0.4.2-20170301.173959-4" :scope "test"]
Not to be a bother, but any idea who I can hound about this? It's a real pain to redeploy sites to a different region because you have to wait ~24 hours for the S3 bucket name to be released.