This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-21
Channels
- # beginners (82)
- # bitcoin (1)
- # boot (38)
- # cider (6)
- # cljs-dev (13)
- # cljsrn (5)
- # clojure (320)
- # clojure-italy (22)
- # clojure-losangeles (6)
- # clojure-russia (55)
- # clojure-spec (25)
- # clojure-uk (48)
- # clojurescript (64)
- # component (16)
- # core-async (6)
- # cursive (54)
- # data-science (2)
- # datascript (2)
- # datomic (8)
- # docker (1)
- # ethereum (1)
- # fulcro (1)
- # garden (1)
- # graphql (16)
- # heroku (6)
- # hoplon (12)
- # jobs (4)
- # juxt (1)
- # leiningen (9)
- # off-topic (39)
- # om (13)
- # om-next (2)
- # onyx (9)
- # pedestal (2)
- # portkey (12)
- # re-frame (25)
- # reagent (6)
- # ring-swagger (4)
- # schema (1)
- # shadow-cljs (10)
- # spacemacs (11)
- # testing (19)
- # uncomplicate (1)
- # unrepl (6)
- # vim (21)
- # yada (3)
@cgrand was looking at the question of “why no check of function-policy here?“: https://github.com/portkey-cloud/portkey/blob/master/src/main/clojure/portkey/core.clj#L468
had to read what I had done, but reason probably was that lambda/import-rest-api
is branch where we create the API for the first time
so figuring that the lambda function should then not have invoke permission for
principal
should probably really parse output of lambda/get-policy
and check that there is a statement that allows
to invoke the function
> Could not find artifact portkey:aws-clj-sdk:jar:0.1.0-SNAPSHOT in clojars (https://clojars.org/repo/)