Hi! I love me some Nomad. We’re using the dispatch job capability to provide a compute backend for our ML efforts. I’m curious if there’s anyway to dynamically (at the time dispatch job API is invoked) set a constraint, or a piece of metadata evaluated by an existing constraint on the job? The use case here is I have multiple auto scaling groups in AWS. The nomad clients have metadata declaring which ASG they’re in. I would like, at dispatch job time, to specify which ASG the job should run in without having to have a job definition per ASG. Is this possible?
I guess this is quite similar to my question from earlier this year: Dynamic resource allocations for parameterized jobs - the answer to which was no so maybe that also applies in this case. I was hoping that via the dispatch metadata overrides, I could override job metadata that could be compared against client metadata