This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-14
Channels
- # announcements (11)
- # babashka (82)
- # beginners (51)
- # calva (11)
- # cider (3)
- # clj-kondo (62)
- # cljdoc (10)
- # cljs-dev (22)
- # clojure (75)
- # clojure-boston (1)
- # clojure-brasil (3)
- # clojure-czech (4)
- # clojure-europe (49)
- # clojure-france (10)
- # clojure-italy (16)
- # clojure-nl (5)
- # clojure-uk (9)
- # clojurescript (69)
- # community-development (33)
- # conjure (12)
- # core-async (6)
- # cursive (2)
- # datalevin (7)
- # datomic (6)
- # graalvm (13)
- # gratitude (2)
- # honeysql (3)
- # introduce-yourself (1)
- # lsp (37)
- # nextjournal (62)
- # off-topic (29)
- # pathom (1)
- # quil (2)
- # reitit (4)
- # releases (2)
- # sci (1)
- # shadow-cljs (28)
- # spacemacs (10)
- # sql (1)
- # tools-build (3)
- # vim (3)
ion: what is a good way to check the latest succeeded deploy rev? My app could print it as "version"
What if we are in the middle of a rolling deployment (i.e. multiple versions are running)? How do we know which version did the request hit?
I'm using on-prem, not cloud, but do use code deploy...so this may not perfectly align with your environment, but what we do is populate the https://docs.oracle.com/javase/tutorial/deployment/jar/packageman.html in MANIFEST.MF as part of our build and then read that back in the running process (e.g. logged on startup, added to response headers, etc.). Our codedeploy descriptor includes a "validate" script which checks that the running version matches the one it (thinks) it just deployed. This helps in cases where, e.g., an old version doesn't cleanly exit and codedeploy scripts think they have deployed a new version, but in reality the old version is still serving requests.