ashb commented on PR #68403: URL: https://github.com/apache/airflow/pull/68403#issuecomment-6125200374
For the executors etc: it feels like the fix is to say "configure it for the worker, so it knows what team it's running for", no? > Dag authors: AIRFLOW_CTX_TEAM_NAME / context["dag_run"].team_name makes the team name available to dag authors Yes, but _why_? Making it available isn't a use case or a justification for why we should do this. Again, aren't workers already exclusive to one team, or a free-for-all, so this value should be pre-configured and not come form the server? Either the executors are per team, or they aren't, but if they aren't can you actually use this value and trust it in anyway? If we still think this is a necessary feature to add, I'd rather this was exposed to user code as `dag.team_name` or something, not via dag run. (The plumbing to get through processes there is another matter, but specifically the way it's interacted with) -- 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]
