I read about worker versioning that is in pre-release but seems like involve a bit of infrastructure stuff in order to have different version of workers running at the same time until the old ones are not use and get deleted.
Note that what we have in doc today (Worker Versioning (Legacy) | Temporal Documentation ) is deprecated and the new API is described here temporal/docs/worker-versioning.md at main · temporalio/temporal · GitHub
Question like
- How can I remove old worker automatically?
- How can I deploy a new version of workers without delete the existing one if there are processing something?
Assuming you don’t have to query closed workflows, you can shutdown the worker when there are no running workflows for the same BuildID the worker has, using the Search Attribute BuildIds
As you mentioned before, this is in pre-release. Have to explore the other versioning strategies described here?
Antonio