UniqueOpts with ByTags argument
We do have ByArgs argument in UniqueOpts but unfortunately it is not good enough for my use case to describe uniqueness of the job (because I have different timestamps, requests id etc in job arguments). Is it possible to add something like ByTags to UniqueOpts for more fine-grained uniqueness control?
@mobiletoly would it work for your use case if you could do uniqueness comparisons against a subset of args (specified by top level JSON field names) instead of all of them? That’s something we’ve talked about before but haven’t yet got around to implementing.
hi @bgentry - yes, it will absolutely work for me.
This should be closed by #590 which will be merged shortly. You can now opt into having uniqueness considerations look at a subset of your job's arguments, instead of all of them.