Closed eelkevanfoeken closed 2 years ago
@eelkevanfoeken We have a script called script/update-deps.clj
. I thought this would fetch all the latest stuff, but apparently it's missing something. Could you take a look there and improve the script? After that we can run it and update the pod.
It seems the deps.edn
already contains proton:
$ less deps.edn | grep proton
com.cognitect.aws/proton {:mvn/version "813.2.963.0" :aws/serviceFullName "AWS Proton"}
I don't think aws-lib.edn
is used anywhere.
There is a list of keys in aws-services.edn
but I don't know how that was generated. It should probably be re-generated in script/update-deps.clj
but from which data?
(def services (into (sorted-set) (clojure.edn/read-string (slurp (io/resource "aws-services.edn")))))
(def *clients (atom {}))
(defn get-client [config]
(get @*clients (get config ::client-id)))
(defn -client [{:keys [api] :as config}]
(if-not (contains? services api)
(throw (ex-info (str "api " api " not available") {:available services}))
(let [config (assoc config
:http-client @http-client)
client (aws/client config)
client-id (java.util.UUID/randomUUID)]
(swap! *clients assoc client-id client)
{::client-id client-id})))
This list and above check was put here by @jeroenvandijk so hopefully he can enlighten us :).
@borkdude I've created a PR with some explaination https://github.com/babashka/pod-babashka-aws/pull/50
Thanks a lot! I'll release a new version.
Released to the pod registry.
Thank you @jeroenvandijk and @borkdude
The pod currently does not support AWS proton. Locally, I did manage to fix the issue by updating the dependency in
deps.edn
, adding the dependency toaws-libs.edn
and adding:proton
to the list inresources/aws-services.edn
, followed by locally compiling the image and running that. If you want I can do a PR?FYI, the following exception is thrown: