Pipeline "promote" flow similar to Heroku

mhuebert · May 27, 2022, 9:36pm

I wanted a way to “promote” a staging app to production (as with Heroku pipelines), so I wrote a little script to parse the registry/repository/tag from the staging image, reconstruct the full path, and pass it to a deploy command pointed at prod.

github.com

sparkboard/sparkboard/blob/ae4057e840f7c1693080e8f99c39ac16f9b98ee0/bb.edn#L7

      
        
            {:tasks {:requires ([cheshire.core :as json]
                                [clojure.java.shell :refer [sh]])
                     :init (do (def staging "sparkboard-jvm-staging")
                               (def prod "sparkboard-jvm"))
                     build (shell "bin/build")
                     deploy (shell "fly deploy -a " staging)
                     promote (let [{:strs [Registry Repository Tag]} (-> (shell {:out :string}
                                                                           (str "fly image show -a " staging " --json"))
                                                                       :out
                                                                       json/parse-string)
                                   image (str Registry "/" Repository ":" Tag)]
                               (shell (str "fly deploy -a " prod " --image " image)))}}

Not sure if there is a built-in/blessed way to do this? An option to get the full image path would be nice (to avoid having to parse JSON).

ignoramous · May 27, 2022, 10:07pm

For my app, every commit to main deploys to “staging” (a separate fly app to “prod”) and when anyone merges in a git tag it deploys the tagged commit to “prod” (note, fly doesn’t yet have notions of envs built-in).

If you desire one env per commit, then fly github action pr-review-apps might come in handy.

See also: Demo: Heroku-style Review Apps