ahilashsasidharan commented on issue #62251: URL: https://github.com/apache/airflow/issues/62251#issuecomment-4028640547
### Summary of Tests I am testing this on a git revision from March 5th, so hopefully not too much has changed. As far as I can tell both Test 1 and Test 2 had the expected results. For Test 3, there seem to be 3 main issues which I am not fully sure if/how they need to be addressed, but this is my initial assessment: 1. There is no check to ensure that team_name is not accepted when the multi team's feature is disabled, which allows you to create a team (i.e., team_a), then turn off the multi team's feature and create a pool with a team via the API, as it will not throw a 500 error since the team exists in the database. I would assume the solution here is to add a check to ensure the multi-team feature is enabled and throw an error when a team is provided when it is disabled. 2. There is no error catching for when a team does not exist and is used to create a pool via the API, leading to the 500 errors, so there may still be unhelpful 500 errors when you try to create a pool with a team that does not exist with the multi team feature enabled (have yet to verify this, but will tomorrow) 3. I could not find an implementation of using the Airflow CLI to create pools with teams. Take what I say with a grain of salt, as I haven't had a chance to verify all of this fully, but leaving this as my initial comment till I can. If these issues haven't already been addressed and you are looking for help on them, I would be happy to work on PRs for any of them as needed. Please also let me know if there any issues with how I ran the tests and if you would like any other scenarios tested. -- 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]
