This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-05-15
Channels
- # babashka (3)
- # beginners (28)
- # calva (8)
- # cider (16)
- # clj-on-windows (4)
- # clojure (69)
- # clojure-europe (29)
- # clojure-norway (42)
- # clojure-uk (4)
- # community-development (5)
- # conjure (3)
- # cursive (18)
- # datomic (68)
- # emacs (23)
- # events (1)
- # honeysql (7)
- # introduce-yourself (1)
- # jobs (1)
- # lsp (11)
- # music (1)
- # observability (3)
- # off-topic (35)
- # other-languages (33)
- # releases (1)
- # remote-jobs (2)
- # ring (18)
- # shadow-cljs (16)
- # timbre (5)
- # tools-deps (9)
I just ran into the missing support for password encryption in settings.xml: https://ask.clojure.org/index.php/13320/support-of-maven-password-encryption-in-tools-deps. I've voted for the issue on Ask. In the meantime, does anyone have a practical workaround where I can avoid keeping unencrypted passwords in settings.xml?
<username>${env.SERVER_USERNAME}</username>
<password>${env.SERVER_PASSWORD}</password>
Works beautifully, thanks! 👍 Though I'd love to see that Ask implemented to avoid keep plaintext password laying around.
I believe there is a patch on that ticket but I’m kind of waiting until I make the transition to the newer set of Maven libs as that may change the impl
the env var is how we do it at my job as well, it works great across teams
They can be fed from password managers agents, or on ci via a runner, etc etc it’s quite handy
we use the 1password cli tool to inject a bunch of env variables for our common tasks with binstubs