This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-06-02
Channels
- # ai (1)
- # aleph (16)
- # announcements (1)
- # architecture (51)
- # babashka (32)
- # beginners (27)
- # calva (3)
- # clerk (1)
- # clojure (49)
- # clojure-art (1)
- # clojure-denver (6)
- # clojure-europe (70)
- # clojure-nl (1)
- # clojure-norway (56)
- # clojure-uk (2)
- # clojuredesign-podcast (4)
- # clojurescript (57)
- # clr (15)
- # community-development (3)
- # conjure (1)
- # core-async (10)
- # data-science (1)
- # datalog (2)
- # datomic (3)
- # emacs (12)
- # events (1)
- # gratitude (4)
- # honeysql (9)
- # hyperfiddle (86)
- # jobs (4)
- # off-topic (10)
- # pedestal (5)
- # portal (11)
- # practicalli (2)
- # reitit (7)
- # releases (3)
- # remote-jobs (1)
- # sql (15)
- # tools-build (8)
- # xtdb (4)
Good morning!
🚆 :flag-be: ➡️ 🇬🇧 and hoping - despite my solidarity :fist::skin-tone-3: - to avoid the ⚡⚡
thoughts on aero secrets handling? https://github.com/juxt/aero#hide-passwords-in-local-private-files
Isn't aero's solution to just not really handle secret but leave it up to the user?
more just that it has #include
and #join
and you can reference those things brought in easily which makes it worth checking in as a development thing (which is my usecase here)
ex at work we have an aero tag #secret, we include secrets via env vars usually, and that tag wraps them in a custom type that will not output the actual value if printed
and on the consumer side, you only deref/unmask the secret value at the last possible moment
that's a decent way to avoid accidental output of private stuff in logs & elsewhere (sentry, telemetry & whatnot)
actually it's oss (undocumented tho): https://github.com/exoscale/cloak/blob/master/src/exoscale/cloak.cljc
the tag is just : (defmethod aero/reader 'secret [ value] (exoscale.cloak/mask value))
We went a different route and redact secret values in our logging code. Haven't thought deeply about trade-offs there.
¡måning & yvening¡
Don’t know if this is useful to anyone but me (the most useful part was probably the making of it), but on the off chance that it is, I’ve been working on this mind map of the “Design in Practice” talk: https://whimsical.com/design-in-practice-PNQ6pHTiU8MdPjcWfN9hbE It’s a great talk, but there’s so much information that it’s hard for me to keep track of the relationships between things without some help. It obviously doesn’t include everything discussed in the talk, but maybe it’s better than nothing. (As a side note, Whimsical is great!)
I'm a big fan of mind maps and have been for years. Shame that Whimsical didn't support mobile so I can't look at it right now:worried:
That's great, thx for sharing! reading it on my android phone right now
@U4ZDX466T Maybe it just doesn't like Bing/Edge on Android? I can read it in Edge (Chromium) desktop and it's great to see the process all laid out like that -- nice work! I've bookmarked it for the future.
@borkdude clojure.walk is not available in babashka, as far as I can tell. If that's how it is, that's how it is, and I'm free to open a PR, I get that 🙂 But I'm wondering if there's a reason that it's not there?
I couldn't see it in the list of available namespaces and libraries
well, great!
I was searching here: https://book.babashka.org/#libraries
docs are always out of date or incomplete, clojure.walk has been in bb from the very beginning
Your second sentence certainly validates the first!
I'm trying, but getting
remote: Permission to babashka/book.git denied to Reefersleep.
fatal: unable to access ' ': The requested URL returned error: 403
borkdude@MBP2019 /tmp $ git clone
Cloning into 'book'...
remote: Enumerating objects: 1790, done.
remote: Counting objects: 100% (411/411), done.
remote: Compressing objects: 100% (166/166), done.
remote: Total 1790 (delta 275), reused 374 (delta 245), pack-reused 1379
Receiving objects: 100% (1790/1790), 748.37 KiB | 3.65 MiB/s, done.
Resolving deltas: 100% (1118/1118), done.
I cloned it fine, the above message is from trying to push my branch
sorry
bit unclear 🙂
cloned directly from yours, pushing a branch directly to yours
maybe not "how it's done" tm
why do you think you, a random person on the internet, can push a branch to my repo? ;)
I'll return to this later
the workflow is usually: make a fork on github, clone that fork using ssh:// (not https://), push your branch and then make a PR
Why ssh over https?
I've done this before with other repos a few times, but I didn't see it in the CONTRIBUTING.md
, so I thought I could get away with pushing a branch directly onto your repo.
I guess it's implied by just being on github and that being the convention there? Or maybe it's even just a git convention for open source projects?
Thank you!
you can never just push something to a repo that you don't own or have the right security access to
Well, I thought having branch pushing abilities open to the public was a thing. But I've never really looked into admin stuff on github.
Thanks for elaborating, I'll keep it in mind for my next PR 🙂
Consider me schooled 🙂
when you are working on a repo of your company, if you can do this, this is because you have access, but this is not the case for repos generally. e.g. I can't push a branch to http://github.com/clojure/clojure, that would be very surprising to me if I could :)
Jawohl!
Maybe I'd know this by heart if I were a more diligent open source contributor :face_with_monocle: