The GitHub Actions job "Tests (AMD)" on airflow.git/fix-secrets-backend-team-name has failed. Run started by GitHub user kaxil (triggered by kaxil).
Head commit for run: b0ca37829f5879731b8150add7a6bd8a800fe509 / Kaxil Naik <[email protected]> Fix older and custom secrets backends breaking on Airflow 3.2 Airflow 3.2 (AIP-67 multi-team) added a `team_name` keyword to the secrets backend API. BaseSecretsBackend.get_connection() forwarded it to get_conn_value() unconditionally, and the core get_*_from_secrets() call sites passed it straight to get_connection()/get_variable(). Any backend whose override predates the keyword (the old (self, conn_id) / (self, key) signature) raised TypeError on every lookup, which the backend-iteration loop swallowed as "not found", so connections and variables silently failed to resolve after upgrading to 3.2. Route those calls through a helper that introspects the override and forwards team_name only when it is accepted (a team_name parameter or **kwargs), omitting it for pre-3.2 signatures so older bundled providers and custom backends keep working -- in both single-team and multi-team deployments -- without being forced to add the parameter. A TypeError from inside an accepting backend is left to propagate, not retried without team_name, so a team-scoped lookup is never silently resolved against the global scope. Applied to the get_conn_value forward in the base class and to the Connection/Variable get_*_from_secrets call sites, which also covers backends overriding get_connection/get_variable directly (e.g. Vault). Report URL: https://github.com/apache/airflow/actions/runs/27227930117 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
