Best practices of task definition deployments

Conductor OSS
1

How do people generally handle task definition deployments?

Currently, I have my workers POST (register) on startup. However, this prevents me from hand changing timeout settings via orkes UI because my timeout values keep reverting every time my worker apps restart. How do people handle this?

  • We could only register/save the task definition if it is missing but that prevents changing workers and definitions at the same time.

  • task definitions don’t have version numbers. Otherwise that would be a good way to know if you want to save a new version

1 Like
2

@joek Hey, thanks for posting!

Wanted to clarify, are you using Conductor OSS (open-source) or Orkes Conductor?

Jeff Bull
Developer Community Manager

3

@jeff.bull Orkes Conductor

1 Like