o-nikolas opened a new issue, #60912: URL: https://github.com/apache/airflow/issues/60912
### Body Each executor needs changes before it can be used in a multi-team setup. The two major requirements are: 1) Ability to read team-based configuration - e.g., two CeleryExecutors may need different brokers, backends, or autoscaling settings, etc for different teams. 2) The executors must be safe to run concurrently within the same scheduler process - e.g. no shared memory/queues, global DB tables, or shared filesystem, etc. This implies different things for different executors; some may need little to no changes some may need many. This is a meta tracking Issue for which executors have been converted. Please comment if you'd like to take on a particular executor. ## Task list: ### Community Supported Executors: - [x] LocalExecutor (#59021) - [x] CeleryExecutor (#60675 ) - [ ] KubernetesExecutor - [ ] EdgeExecutor ### Third Party Executors (Providers) #### Amazon - [x] AwsEcsExecutor (#55003) - [ ] AwsBatchExecutor - [ ] AwsLambdaExecutor ### Committer - [x] I acknowledge that I am a maintainer/committer of the Apache Airflow project. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
