Add AWS proton support about pod-babashka-aws HOT 8 CLOSED

@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.

from pod-babashka-aws.

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"}

from pod-babashka-aws.

I don't think aws-lib.edn is used anywhere.

from pod-babashka-aws.

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 :).

from pod-babashka-aws.

@borkdude I've created a PR with some explaination #50

from pod-babashka-aws.

Thanks a lot! I'll release a new version.

from pod-babashka-aws.

Released to the pod registry.

from pod-babashka-aws.

Thank you @jeroenvandijk and @borkdude

from pod-babashka-aws.