This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-04
Channels
- # babashka (17)
- # beginners (82)
- # calva (42)
- # clj-commons (9)
- # cljdoc (2)
- # cljsrn (3)
- # clojure (142)
- # clojure-europe (12)
- # clojure-nl (1)
- # clojure-sg (1)
- # clojure-uk (14)
- # clojurescript (22)
- # community-development (3)
- # cryogen (12)
- # cursive (15)
- # data-science (13)
- # datomic (11)
- # deps-new (8)
- # emacs (3)
- # fulcro (31)
- # gratitude (7)
- # holy-lambda (8)
- # honeysql (6)
- # introduce-yourself (1)
- # jackdaw (11)
- # jobs-discuss (7)
- # kaocha (1)
- # malli (8)
- # other-languages (9)
- # pathom (14)
- # pedestal (1)
- # polylith (3)
- # portal (12)
- # re-frame (3)
- # react (3)
- # reagent (4)
- # releases (3)
- # reveal (7)
- # ring (11)
- # shadow-cljs (17)
- # specter (3)
- # sql (1)
- # timbre (2)
- # tools-deps (122)
- # xtdb (18)
if I have deps defined in bb.edn I also have them in deps.edn, should bb --nrepl automatically pull them? Else how do I pull/load them
@benjamin.schwerdtner deps are not included automatically from deps.edn
. Right now you'll have to duplicate them in bb.edn
How can I escape single quotes in bb script in clj? The --description string fails in the java sh command but work in terminal
aws iam create-role --role-name account-role --description 'Cloud Ops role' ...
I think the purpose of the single quotes at the terminal is to ask the shell to pass to the aws command Cloud Ops Role as a single (string) argument. I would try leaving out the single quotes and passing what's between them as the next item in the array of strings after --description, like: (sh ... "--description" "Cloud Ops role" ... )
This does not work because cli expects to quote the strings with spaces like 'Cloud Ops role'
@dennisa I recommend using babashka.process/tokenize
if you want to tokenize a shell string into multiple parts.
E.g.:
user=> (babashka.process/tokenize "hello there 'i am a string'")
["hello" "there" "i am a string"]
As @U06C3GHJR was saying: you can omit the single quotes around 'i am a string'` since in shells this just denotes that this is a single string
tokenize had resolved it, by own version of tokenize was too basic for this use case. Thanks!
This is list of companies using babashka: https://github.com/babashka/babashka/blob/master/doc/companies.mdhttps://t.co/svvkxvt4Pg?amp=1 Is your company using babashka too, let me know in the issue!
This works fine with bash
aws iam update-role --role-name account-role-ops --description "Cloud Ops-IaC role" --p istest
or
aws iam update-role --role-name account-role-ops --description 'Cloud Ops-IaC role' --p istest
But the same command fails with sh