Motivation: Why do you think this is important?
ArrayJob proto has 4 different primitive values that can be filled in. We can cleanup the dependency on a proto and move these params to configs on the TaskTemplate.
Goal: What should the final outcome look like, ideally?
Deprecate ArrayJob proto and leverage TaskTemplate.Config map instead.
This frees up the Custom field to the individual tasks' which opens up the possibility of defining Array Jobs on custom task types.
Describe alternatives you've considered
N/A
Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
Motivation: Why do you think this is important?
ArrayJob proto has 4 different primitive values that can be filled in. We can cleanup the dependency on a proto and move these params to configs on the TaskTemplate.
Goal: What should the final outcome look like, ideally?
Deprecate ArrayJob proto and leverage TaskTemplate.Config map instead.
This frees up the Custom field to the individual tasks' which opens up the possibility of defining Array Jobs on custom task types.
Describe alternatives you've considered
N/A
Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?