This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-28
Channels
- # asami (13)
- # babashka (6)
- # beginners (38)
- # calva (14)
- # cider (15)
- # circleci (13)
- # clj-kondo (4)
- # cljsrn (18)
- # clojure (164)
- # clojure-bay-area (3)
- # clojure-europe (46)
- # clojure-italy (8)
- # clojure-losangeles (3)
- # clojure-norway (3)
- # clojure-sweden (24)
- # clojure-uk (115)
- # clojurescript (79)
- # cursive (11)
- # datomic (24)
- # docker (2)
- # events (9)
- # figwheel-main (31)
- # fulcro (5)
- # honeysql (6)
- # jackdaw (7)
- # jobs (3)
- # jobs-discuss (16)
- # joker (1)
- # kaocha (6)
- # keechma (1)
- # lein-figwheel (1)
- # malli (6)
- # pathom (10)
- # podcasts-discuss (13)
- # practicalli (3)
- # react (4)
- # reagent (3)
- # reitit (8)
- # remote-jobs (3)
- # shadow-cljs (21)
- # sql (12)
- # tools-deps (20)
- # xtdb (24)
@borkdude @slipset We’ve launched setup workflows: https://circleci.com/blog/introducing-dynamic-config-via-setup-workflows/ This allows you to run code to generate config as part of the workflow.
This will allow you you to write a config.edn
and use a setup workflow to convert the config.edn to YAML and run it.
(using jet
?)
Awesome! I'm currently doing that using bb
(babashka) but I just commit the yaml into the git repo
jet
only supports JSON, EDN and Transit, else the name would not be right anymore ;)
4
YAML isn’t valid JSON though!
yes it is