This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-21
Channels
- # beginners (201)
- # boot (125)
- # cider (3)
- # cljs-dev (21)
- # cljsrn (165)
- # clojars (8)
- # clojure (332)
- # clojure-belgium (1)
- # clojure-gamedev (8)
- # clojure-russia (75)
- # clojure-spec (25)
- # clojure-uk (96)
- # clojurebridge (2)
- # clojurescript (130)
- # code-reviews (16)
- # cursive (26)
- # datomic (20)
- # devops (6)
- # emacs (6)
- # hoplon (90)
- # jobs (9)
- # luminus (2)
- # off-topic (4)
- # om (65)
- # onyx (5)
- # pedestal (4)
- # protorepl (6)
- # re-frame (34)
- # reagent (12)
- # ring (4)
- # ring-swagger (7)
- # specter (2)
- # test-check (8)
- # untangled (2)
- # vim (1)
- # yada (6)
robert-stuttaford <off> CircleCI supports env variables, did you try to use it for handle multiple aws accounts?</off>
we did. we currently have to store creds in circle.yml and that’s bad.
yeah, it's not good idea to store credentials into code. However you could set up the creds into the web-interface of Circle
and it would be more securely because noone coulld see you creds even has access to the web-ui
it only supports one set of creds. we need to namespace the creds by git branch, because we use multiple aws accounts; one per env
trust me, i’m pretty clear on this; CircleCI doesn’t have the support we need
anyway. offtopic 🙂
Maybe there's a better channel for this? 🙂
yep, sorry Sean!