potiuk commented on issue #20969: URL: https://github.com/apache/airflow/issues/20969#issuecomment-1016971298
> I am using the `APP` variable for other purposes and not for Airflow nor Celery. > > The issue is that there aren't any information around this and it wasn't clear why the worker fails to start. There are probably plenty other variables that you can set and fail things. There are plenty other variables that should not be overridden - HOME, PATH, TZNAME to name a few. It's a very bad practice to use "generic" variable names like that - the usual approach is tha tyou should prefix it with your - likely unique - application name `MY_OWN_APPLICATION_APP`. Unfortunately environment variables do not have namespace - this is a general property of ENV variables, not Airflow issue. You can have plenty other tools installed that could use them. I suggest to raise an issue to Celery as apparently they are not folowing those good practices there as well. If you think it would be worth to add documentation about it - feel free to make PR about it. But this is not a bug of Airlfow. -- 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]
