andrewgodwin commented on pull request #15212: URL: https://github.com/apache/airflow/pull/15212#issuecomment-813671560
Honestly, I agree, I was just following along with the original ticket's suggestion since nobody suggested an explicit error instead so I presumed there was implicit acceptance. I can update the PR to raise an exception instead, but leave the indirection via `utils.platform` in order to have a single place the error is caught/raised. Generally, though, I _have_ found that a surprising number of tools will happily work without an actual user record, so there is a user expectation here when they're firing things into Docker. I think it doesn't make sense to match that given Airflow is relatively dependent on user env/environment variables, but I'll see if I can make an error message that is nice enough to stop duplicate issues like #9963 being opened. -- 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: us...@infra.apache.org
