potiuk commented on pull request #16048: URL: https://github.com/apache/airflow/pull/16048#issuecomment-848083913
Actually It's expected, and I see no problems with having them in the list. I do not think it introduces any problem. The connection type is really UI-only change (that drives the selection of fields automatically mapped from extras to fields in the UI). There is no other effect of the connection type selected - whether it's HTTP or Airbyte, makes no difference whatsoever - it's the connection id that matters. So IMHO having the specific Airbyte/Dingding etc. connections is harmless (and actually it's good for consistency). Yes - it makes connection list longer, but only if you have the providers installed, which I think is a good reason on its own to show those connection types in the list. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
