kaxil commented on issue #51816: URL: https://github.com/apache/airflow/issues/51816#issuecomment-2980495661
> Assuming we can detect the case when this is being imported from doing `python mydag.py` (which I'm 95% sure we can, so that is the 'easy' part) how should we actually obtain a value/variable? > > I.e. ignoring all practicialities or other issues, what _should_ this do, given the increased security model in Airflow 3 of not allowing unfettered DB access? Since we allow that in the actual dag parsing models (as it goes via DAG processor -> Supervisor comms -> Variable), we should do the same for dag.test. Now regarding the security model, currently Task Exec API is tied with Task Identity so this becomes a no-go. But that's a breaking change. (Unless ofcourse we want to include DAG file identity too somehow). -- 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]
