This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-25
Channels
- # bangalore-clj (5)
- # beginners (225)
- # boot (36)
- # cider (1)
- # clara (2)
- # cljsjs (1)
- # clojure (76)
- # clojure-belgium (1)
- # clojure-conj (1)
- # clojure-india (4)
- # clojure-italy (5)
- # clojure-korea (1)
- # clojure-russia (22)
- # clojure-spec (35)
- # clojure-uk (52)
- # clojurescript (67)
- # community-development (17)
- # core-logic (2)
- # cursive (2)
- # datascript (28)
- # datomic (44)
- # emacs (1)
- # funcool (3)
- # hoplon (14)
- # lein-figwheel (2)
- # leiningen (2)
- # luminus (3)
- # midje (3)
- # mount (2)
- # nyc (2)
- # om (54)
- # om-next (1)
- # onyx (30)
- # re-frame (57)
- # reagent (19)
- # ring-swagger (23)
- # slack-help (10)
- # spacemacs (2)
- # specter (1)
- # vim (23)
Morning
(if (= brexit brexit) "I'm off back to bed" "good morning, I love the world")
@jonpither the Mastodon C crew do yes
@jonpither I need to run (not working today) worth talking to @otfrom and @elise_huard as well.
@jonpither our current use of terraform is within one region at a time (multiple-AZ). We do use it in different regions though.
There is no reason why it wouldn't work cross-region, we just have no use for it atm
I.e. I'm playing with having a separate tfvars file for each region so I could re-use everything else
thanks @jasonbell and @elise_huard
@jonpither iāve seen some examples of using symlinks to have multiple folders, and thus multiple tfstate files
https://charity.wtf/2016/03/30/terraform-vpc-and-why-you-want-a-tfstate-file-per-env/ seems to be the sort of thing iām thinking of
we have multiple named environments, each has itās own state - using bash+python scripting so you specify ābootstrap-environment Foo-tickā and it creates a āFoo-tick" environment.
(the ātickā is because weāre trying to do nightly environment re-builds - phoenix environments - so each day we build ātockā and tear down ātickā)
@glenjamin I'm using remote state in an s3 bucket... but not sure if it's possible to switch between remote states...
No - database storage is going to be shared (still working out how) and while ātickā and ātockā are both up, they replicate state across both.
I worked on a system once that reset all dev envs every night, but often failed to rebuild. So itād be 1pm before it was working the next day, and then youād have a few hours to get work done before it was blatted
@glenjamin makes sense your approach
@glenjamin ow - that sounds painful.
jonpither I though terraform was getting it from ~/.aws/config where I have
[default]
region = eu-west-1
So you should be able to run it once with one region then with another?@glenjamin sounds like system designed by someone who actually worked for a competitor and sabotaged the project successfully.
heh, it was the sort of place where theyād hit a problem, implement a tool-based solution and never review it
I assume there was one production issue once caused by someone losing track of what changes theyād made to a dev environment