vincbeck commented on PR #37638: URL: https://github.com/apache/airflow/pull/37638#issuecomment-1989411951
> I think that for a lot of the tests just need to creatively look at the way how we initialize things > > ``` > ValueError: The name '/auth/fab/v1' is already registered for a different blueprint. Use 'name=' to provide a unique name. > ``` > > This one repeates ofte and for example indicates (I think) that we have to add a custom name (for example derived with provider name) whenever we register a blueprint from FAB provider (because we register it twice - once for backwards compatibility and once for the new "target" URL. > > @vincbeck ? > > And @VladaZakharova @Taragolis -> maybe you could take a look as well - I feel once we have the PR green we should be able to take a close review and do some testing together to see if the security / performance / way how we register and use the API are cool. I'd really love it if we could get it in in one of the 2.9.0 rc-s if only possible :) I think it is a test issue. The API works fine when I run Airflow with Breeze. Also when I run individually `tests/api_connexion/endpoints/test_connection_endpoint.py` (`breeze testing tests tests/api_connexion/endpoints/test_connection_endpoint.py`), it succeeds. Which might indicate that tests are conflicting with each others (leaving some resources behind). I keep investigating -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
