Sync the self-hosting stack

kubernetes/03-migrate-job.yaml

@@ -46,7 +46,7 @@ spec:
   parallelism: 1
   completions: 1
   # Two retries, because the failures worth retrying are transient (a database not finished failing
-  # over). A schema that Prisma REFUSES is not transient and must not be retried into submission —
+  # over). A schema `jarvis migrate` REFUSES is not transient and must not be retried into submission —
   # it is refused for a reason, and the reason is printed.
   backoffLimit: 2
   # A migration that has not finished in fifteen minutes is stuck, not slow, and the rollout is
@@ -70,7 +70,7 @@ spec:
           # THE SAME IMAGE, by the same digest, as the API that is about to roll. A migration from a
           # different build is a schema that matches nothing.
           image: git.luxit.be/luxit/jarvis-api@sha256:REPLACE_ME
-          command: ["/usr/local/bin/migrate.sh"]
+          command: ["jarvis", "migrate"]
           envFrom:
             - configMapRef:
                 name: jarvis-api-config
@@ -94,8 +94,8 @@ spec:
             # nobody having decided to — survivable on one container, not during a rolling update
             # where the previous generation is still selecting it.
             #
-            # Without the flag the phase REFUSES, prints which columns it would have dropped, and
-            # fails the Job — so the rollout stops and nothing is serving a half-migrated schema.
+            # Without it a pending migration that drops a table or a column is REFUSED, naming them,
+            # and fails the Job — so the rollout stops and nothing is serving a half-migrated schema.
             # Set it to "true" for the ONE deploy where that drop is intended, then remove it.
             - name: SCHEMA_ACCEPT_DATA_LOSS
               value: "false"