MatrixManAtYrService opened a new issue #22392: URL: https://github.com/apache/airflow/issues/22392
### Apache Airflow version 2.2.4 (latest released) ### What happened I created a connection like: ``` airflow connections add fsconn --conn-host /tmp --conn-type File ``` When I really should have created it like: ``` airflow connections add fsconn --conn-host /tmp --conn-type fs ``` While using this connection, I found that FileSensor would only work if I provided absolute paths. Relative paths would cause the sensor to timeout because it couldn't find the file. Using `fs` instead of `File` caused the FileSensor to start working like I expected. ### What you think should happen instead Ideally I'd have gotten an error when I tried to create the connection with an invalid type. Or if that's not practical, then I should have gotten an error in the task logs when I tried to use the FileSensor with a connection of the wrong type. ### How to reproduce _No response_ ### Operating System debian (in docker) ### Versions of Apache Airflow Providers n/a ### Deployment Astronomer ### Deployment details `astro dev start` ### Anything else _No response_ ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
