This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-08
Channels
- # aws (9)
- # beginners (69)
- # boot (14)
- # cider (26)
- # cljs-dev (56)
- # cljsrn (9)
- # clojars (4)
- # clojure (229)
- # clojure-brasil (1)
- # clojure-france (11)
- # clojure-greece (2)
- # clojure-italy (4)
- # clojure-mke (6)
- # clojure-serbia (6)
- # clojure-spec (83)
- # clojure-uk (38)
- # clojurescript (171)
- # core-async (3)
- # cursive (11)
- # data-science (11)
- # datomic (27)
- # emacs (113)
- # funcool (6)
- # hoplon (4)
- # jobs (1)
- # luminus (13)
- # lumo (44)
- # off-topic (148)
- # onyx (5)
- # overtone (1)
- # pedestal (4)
- # powderkeg (1)
- # proton (2)
- # re-frame (150)
- # reagent (16)
- # ring-swagger (43)
- # spacemacs (4)
- # specter (36)
- # vim (4)
- # yada (10)
I’m having a bit of difficulty getting the incantation right that would allow me to point my aws calls to the local … localstack
ah, I think I found the issue. The application from which I’m invoking my AWS code needs some exclusions; when used from a fresh repo, I simply need to use amazonica’s with-credential
and then a fake key, secret, and the local url for the localstack service. Cool stuff 🙂
and my problem was solved by moving amazonica’s decl in project.clj nearer to the top, before several other libraries that depend on apache http libs - lesson which I didn’t know; ordering matters: )
@derwolfe if you specify :pedantic? :abort
in your project.clj
it will bork if there are any incompatible dependencies and ordering will stop mattering
@mccraigmccraig oooh, good to know. I’ll give that a try 🙂
(you will then have to specify sufficient exclusions that there are no more incompatible dependencies to stop it borking - i prefer that you are forced to be explicit like this)