The GitHub Actions job "Tests (AMD)" on airflow.git/gate-env-secret-team-refusal-on-multi-team has failed. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: ae3065f5a776f9499b49af7a8296f7a5f8d1060a / Jarek Potiuk <[email protected]> Refuse separator-bearing env secret ids only in multi-team mode The environment variables backend refuses any connection or variable id carrying the team namespace separator, because such an id cannot be attributed to a team unambiguously. That refusal fires unconditionally, including in deployments that never enabled multi-team mode, where an ordinary id that happens to contain `___` is silently reported as missing. No team scoped secret can be read while multi-team is off -- the lookups are only ever given a team name in that mode -- so the id has a single meaning there and nothing needs refusing. This is the core half of the same regression fixed for the AWS, Key Vault, Google Secret Manager and Lockbox backends in #71078. Report URL: https://github.com/apache/airflow/actions/runs/30972582537 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
