spinning more than one dask cluster deletes prior dask task definitions

[jkanche]

when using AWS ECS clusters, spinning up more than one dask cluster deletes the other dask created task definition. I'm guessing its looking up task definitions by tag and removing others?

[jacobtomlinson]

It should only delete task definitions that aren't associated with any running clusters.

https://github.com/dask/dask-cloudprovider/blob/7b214adc87f1026d8e2149fa109276f6e2497606/dask_cloudprovider/aws/ecs.py#L15790L1585

We define active clusters as clusters with runningTasksCount or pendingTasksCount greater than zero.

Could you share an example of the behaviour you are seeing?