Description
Make secrets backends receive the DAG bundle's team_name during DAG file parsing, the same way they receive it during task execution.
This makes team-scoped resolution consistent between parse time and run time, so a team-scoped backend (for example one routing to a per-team Vault by team_name) can resolve config for a bundle's DAGs while they are being parsed.
Today team_name is always None at parse time.
Use case/motivation
Multi-team dynamic DAG generation that reads a team-scoped connection or variable at parse time. A bundle belongs to a team, but a team-scoped secrets backend can resolve config for that bundle's tasks and not for parsing of the same bundle's files, because team_name is None there.
The bundle to team mapping needed to close the gap is already in the DAG processor.
Related issues
#65530
Are you willing to submit a PR?
Code of Conduct
Description
Make secrets backends receive the DAG bundle's team_name during DAG file parsing, the same way they receive it during task execution.
This makes team-scoped resolution consistent between parse time and run time, so a team-scoped backend (for example one routing to a per-team Vault by team_name) can resolve config for a bundle's DAGs while they are being parsed.
Today team_name is always None at parse time.
Use case/motivation
Multi-team dynamic DAG generation that reads a team-scoped connection or variable at parse time. A bundle belongs to a team, but a team-scoped secrets backend can resolve config for that bundle's tasks and not for parsing of the same bundle's files, because team_name is None there.
The bundle to team mapping needed to close the gap is already in the DAG processor.
Related issues
#65530
Are you willing to submit a PR?
Code of Conduct