This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-24
Channels
- # announcements (12)
- # aws (11)
- # babashka (1)
- # beginners (73)
- # cider (4)
- # clj-kondo (2)
- # cljsrn (4)
- # clojars (2)
- # clojure (68)
- # clojure-europe (8)
- # clojure-nl (5)
- # clojure-spec (6)
- # clojure-sweden (1)
- # clojure-uk (29)
- # clojurescript (41)
- # conjure (22)
- # datomic (33)
- # docker (58)
- # duct (3)
- # emacs (8)
- # events (1)
- # expound (3)
- # figwheel-main (5)
- # fulcro (33)
- # graphql (2)
- # kaocha (2)
- # lambdaisland (39)
- # leiningen (1)
- # nrepl (49)
- # nyc (1)
- # off-topic (77)
- # pathom (1)
- # re-frame (33)
- # reagent (28)
- # reitit (1)
- # rewrite-clj (2)
- # shadow-cljs (195)
- # spacemacs (1)
- # sql (60)
- # tools-deps (13)
- # vim (18)
- # xtdb (46)
Curious if anyone has thought about how one would dynamically change the AWS profile from the REPL for aws-api. We have some "default" clients def
'ed in many locations. I can dynamically change the aws.profile Java prop but, afaict, there's no way to bust the creds cache on all those def'ed clients. The use case for changing profiles seems common enough -- I'd like to have my REPL running for a while and switch between my "dev" and "prod" aws profiles.
There could be dozens of top level def'ed clients. Each one would need to be eval'ed after changing the profile.
you should pass around clients as arguments, so if you want new ones with different credentials you can create new ones and pass those around to your functions
Totally agree. We have a lot of old code that would require a decent amount of eng resources to change to not be top-level def'ed. It'd be great to do at some point... Was trying to see if there was some sort of short-term solution to this.
there is https://github.com/cognitect-labs/aws-api/blob/master/src/cognitect/aws/credentials.clj#L48 I am not sure what it would take to call it