feat: Max task concurrency irrespective of the tenant queue #3235
Description
Is your feature request related to a problem? Please describe.
I have to process 1000s of images and I have third party api rate limit of 20 parallel processing.
I want to allow user to be able to consume only 1 concurrency while maintaining task concurrency to 20
As soon as I use concurrency key it takes 1 per user but does not respect 20 limit and tasks start failing.
similar scenario, I like to process my order webhooks in parallel but I have to make sure I am processing webhooks for each order in sequence. I dont want to spin 100s of workers and block all other tasks while working on each order separately.
Describe the solution you'd like to see
There should be a config maxGlobalConcurrency: 10 in task definition and that should be respected when spinning workers. by default this value can be the global environment limit in case the value is not provided. this way there is no change needed to existing task definitions.
Describe alternate solutions
Not explored
Additional information
No response