For example, going from temporalio/server:1.19.1 to 1.20.1
I’m not clear if I need to manually run “auto-setup” again when upgrading, or if it does DB updates automatically (if needed).
I think because these are consecutive (1.19 → 1.20) we don’t need to do anything special here and can just switch out the container image tag - is that right?
The docker image you update to includes the latest version binary and schema files. After update image version you should only need to update the existing schema, see for example here. I believe if you are running auto-setup, the auto-setup.sh script should take care of that part.
That’s what I’m confused about. I used the auto-setup images while provisioning the server. Now we’re in run mode I switched to the “plain” server docker images (i.e. temporalio/server:1.19.1)
So if I just swapped to temporalio/server:1.20.1, it would not automatically run the schema updates? Should we use the auto-setup image full time instead?
I’ve not set that env var anywhere in production (should we?), I was just trying to extract the upgrade command we need to run from the auto-setup script