This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-13
Channels
- # adventofcode (36)
- # aleph (1)
- # announcements (7)
- # aws (4)
- # babashka (14)
- # beginners (61)
- # calva (79)
- # cider (19)
- # clojure (48)
- # clojure-austin (1)
- # clojure-australia (2)
- # clojure-czech (2)
- # clojure-europe (46)
- # clojure-france (8)
- # clojure-nl (19)
- # clojure-uk (4)
- # clojuredesign-podcast (14)
- # core-logic (42)
- # data-science (3)
- # datalevin (8)
- # datomic (76)
- # events (1)
- # figwheel-main (9)
- # fulcro (6)
- # helix (1)
- # holy-lambda (1)
- # honeysql (2)
- # jobs (2)
- # jobs-discuss (20)
- # leiningen (5)
- # lsp (87)
- # minecraft (11)
- # nextjournal (4)
- # off-topic (17)
- # practicalli (1)
- # reagent (22)
- # reitit (8)
- # releases (3)
- # rum (2)
- # shadow-cljs (18)
- # sql (11)
- # tools-build (5)
- # tools-deps (9)
- # xtdb (20)
I am trying to run `lein.classpath/classpath` in an AWS Lambda, but I am getting the error
Cannot access using the registered transporter factories: FileTransporterFactory, WagonTransporterFactory
I've been using https://github.com/s3-wagon-private/s3-wagon-private to download private dependencies from S3. I've already configured a role attached to the Lambda to allow it access the S3 bucket:
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"s3:List*",
"s3:Get*"
],
"Resource": [
"arn:aws:s3:::my-bucket*"
],
"Effect": "Allow"
}
]
}
And this is the project.clj that is being used:
(defproject ....
:repositories [["central" {:url " " :snapshots false}]
["clojars" {:url " "}]
["nu-maven" {:url " " :snapshots false :sign-releases false}]]
...)
Does anyone know what could be the issue?I forgot to mention, but we are also changing dynamically the project.clj
to add :local-repo "/tmp/m2"
as the Lambda doesn't have write permission on ~/.m2
We also added the environment variable LEIN_HOME="/tmp/lein"
due to the same permission issue
Doesn't sound like a generic Lein issue to me, perhaps you'd have better luck getting a full stacktrace and creating a github issue in the plugin's repo
1
It makes sense. I will also open there an issue about this bug