This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-20
Channels
- # announcements (10)
- # aws (4)
- # babashka (71)
- # beginners (30)
- # calva (61)
- # cherry (1)
- # cider (16)
- # clj-kondo (3)
- # clj-on-windows (4)
- # cljsrn (1)
- # clojure (28)
- # clojure-austin (2)
- # clojure-bay-area (1)
- # clojure-europe (45)
- # clojure-hungary (1)
- # clojure-nl (1)
- # clojure-norway (26)
- # clojure-sweden (14)
- # clojure-uk (11)
- # clojurescript (39)
- # core-async (3)
- # core-typed (11)
- # datomic (68)
- # fulcro (7)
- # keechma (1)
- # lsp (29)
- # malli (5)
- # off-topic (57)
- # other-languages (13)
- # pathom (4)
- # rdf (7)
- # reagent (7)
- # reitit (6)
- # releases (1)
- # schema (8)
- # shadow-cljs (86)
- # sql (22)
- # squint (1)
- # vim (8)
- # xtdb (12)
Has anyone effectively used datalog (datomic, juxt, datascript, etc..) to manage and organize there cloudformation information?
Having to use the aws console to go from my cf stack -> resources -> other info is fairly exhausting. I'm thinking something like: [?s :stack/name "test"] [?s :stack/resource ?res] [?res :resource/name "repo"] [?res :cloudwatch/logs ?logs] where logs is the url of the log that you can then query against to get information like events or the fact that my cf deploy failed bc, etc...
The resource mapping will be tricky. You may be able to get by with a 3rd party tool like https://www.cloudquery.io/.
What do you mean resource mapping? I'm thinking the resource name to arn mapping