This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-12
Channels
- # aleph (22)
- # aws (7)
- # babashka (17)
- # beginners (69)
- # chlorine-clover (9)
- # cider (2)
- # clj-kondo (3)
- # cljdoc (30)
- # clojure (113)
- # clojure-dev (30)
- # clojure-europe (11)
- # clojure-italy (2)
- # clojure-nl (16)
- # clojure-spec (1)
- # clojure-sweden (3)
- # clojure-uk (17)
- # clojurescript (77)
- # cryogen (12)
- # data-science (5)
- # datomic (27)
- # duct (2)
- # emacs (37)
- # fulcro (24)
- # graphql (2)
- # kaocha (1)
- # lambdaisland (27)
- # leiningen (4)
- # off-topic (15)
- # onyx (1)
- # other-lisps (3)
- # re-frame (94)
- # reagent (2)
- # reitit (20)
- # ring (1)
- # shadow-cljs (66)
- # spacemacs (5)
- # sql (59)
- # tools-deps (140)
- # vim (1)
- # xtdb (17)
Weird learning of the day: EBS volume prices are based on the month of the year. i.e., the cost per volume gib changes based on the length of the month. Very strange.
😮 4
Could we perhaps have the ability to specify the :api as a part of the op-map? We have tons of code that ends up looking like this:
{::ec2-client (aws/new-client {:api :ec2})
::rds-client (aws/new-client {:api :rds})
::cw-client (aws/new-client {:api :monitoring})
::autoscaling-client (aws/new-client {:api :autoscaling})
::lb-v1-client (aws/new-client {:api :elasticloadbalancing})
::lb-v2-client (aws/new-client {:api :elasticloadbalancingv2})}
There doesn't seem to be a reason for keeping them separate. I suppose we could implement this ourselves.