This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-28
Channels
- # announcements (4)
- # aws (2)
- # babashka (56)
- # beginners (43)
- # calva (71)
- # clj-kondo (25)
- # cljs-dev (29)
- # clojure (103)
- # clojure-dev (9)
- # clojure-europe (55)
- # clojure-gamedev (8)
- # clojure-nl (5)
- # clojure-norway (5)
- # clojure-uk (4)
- # clojured (1)
- # clojurescript (56)
- # copenhagen-clojurians (1)
- # core-async (2)
- # cursive (16)
- # datomic (5)
- # deps-new (18)
- # emacs (9)
- # events (3)
- # fulcro (45)
- # graphql (2)
- # gratitude (2)
- # kaocha (6)
- # lambdaisland (8)
- # lsp (72)
- # meander (41)
- # missionary (5)
- # nextjournal (52)
- # off-topic (2)
- # pathom (12)
- # pedestal (2)
- # practicalli (1)
- # re-frame (6)
- # reitit (5)
- # releases (1)
- # reveal (1)
- # specter (3)
- # sql (4)
- # tools-deps (22)
- # vim (8)
- # wasm (1)
- # xtdb (22)
Hello! I’m going to finally upgrade the cloud from 781 to 931. I’ve already tested our ions app with 931 in a separate account, upgraded code to work with API Gateway and cloudfront / custom domains - it’s all right. The question is: I want to change the name of our primary compute group 🙂 so instead of upgrading both stacks, I’m going upgrade only storage stack, and delete the primary compute stack and create a new primary (with new name). Are there any troubles to expect? (i.e. some AWS resources won’t be deleted and naming troubles may occur, etc.)?
As long as you are re-naming compute this should be fine. Primary can be named whatever you would like and pointed at the system storage template.
@U1QJACBUM Thanks!
Shoot me an e-mail if you run into anything <mailto:[email protected]|[email protected]> 🙂