This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-21
Channels
- # announcements (10)
- # aws (10)
- # babashka (23)
- # beginners (111)
- # biff (8)
- # calva (25)
- # clj-kondo (9)
- # cljsrn (4)
- # clojure (72)
- # clojure-belgium (6)
- # clojure-europe (50)
- # clojure-germany (2)
- # clojure-nl (1)
- # clojure-norway (6)
- # clojure-uk (1)
- # datahike (3)
- # emacs (10)
- # graalvm (19)
- # graphql (3)
- # juxt (7)
- # kaocha (9)
- # malli (23)
- # nbb (20)
- # pathom (17)
- # pedestal (6)
- # polylith (11)
- # portal (8)
- # remote-jobs (3)
- # shadow-cljs (18)
- # sql (3)
- # tools-deps (20)
Hi! Because we just ran into this at work, I'd like to raise the profile of https://github.com/cognitect-labs/aws-api/issues/181 and see where folks are in terms of Jetty 9/10/11?
I asked the same question not long ago: https://clojurians.slack.com/archives/C09N0H1RB/p1664810477149209 - basically there will be a new version of aws-api that will allow you to bring your own HTTP client and opt-out of bundled jetty http client
and yeah, we're blocked from moving to jetty10 for the same reason - at least in the services that depend on aws-api
Yeah, @U0ENYLGTA mentioned that in the ticket. I was hoping to provoke an update on the status of those plans 🙂
Well, color me provoked: https://github.com/cognitect-labs/aws-api/issues/181
Is there an update on the status of this issue, @U0ENYLGTA?
@U04V70XH6 did you move to awyeah? How has that worked out?
For us, it was a drop-in replacement for the way we were using S3 -- but that's the only thing we do with AWS via Clojure right now.
(and we're on Jetty 11 now in production, soon to move to Jetty 12)