This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-10
Channels
- # announcements (10)
- # aws (5)
- # babashka (81)
- # babashka-sci-dev (4)
- # beginners (100)
- # calva (60)
- # clj-kondo (34)
- # clojars (1)
- # clojure (30)
- # clojure-austin (12)
- # clojure-berlin (1)
- # clojure-europe (45)
- # clojure-italy (5)
- # clojure-losangeles (9)
- # clojure-nl (3)
- # clojure-norway (10)
- # clojure-spec (1)
- # clojurescript (8)
- # community-development (2)
- # conjure (5)
- # cursive (10)
- # data-science (2)
- # datalog (1)
- # emacs (4)
- # events (10)
- # fulcro (6)
- # jobs-discuss (8)
- # lambdaisland (3)
- # leiningen (2)
- # luminus (5)
- # membrane (61)
- # off-topic (8)
- # portal (5)
- # releases (20)
- # sci (25)
- # scittle (6)
- # shadow-cljs (25)
- # testing (6)
- # xtdb (11)
Is there anything to make aws respect change sets so that you can always roll forward? The headache is that if a aws cloudformation change set fails, you get stuck in some state and you have to delete the stack to try again. Which isn't ideal. Then when you go to delete the stack, that too can fail because the stack can't recursively delete things like s3 buckets. Does terraform improve on this?
most of the time you can: • re-apply and TF will resolve the changes and get you into correct state • you can taint selected resources to recreate them after next plan+apply cycle
Why hasn't aws done this? i'm baffled, do they just not care to match expectations with modern devops functionality?