The GitHub Actions job "Tests (AMD)" on 
airflow.git/reject-team-names-colliding-on-case has failed.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
e8d5fb347f53447fe55f844364b4b43049fe8ee0 / Jarek Potiuk <[email protected]>
Reject team names that differ only in case

Team names are case sensitive -- `data_eng` and `Data_Eng` are two distinct
teams -- but the environment secrets backend upper-cases the team name when it
builds the variable name, so both resolve `AIRFLOW_CONN__DATA_ENG___<ID>`. Two
such teams share a single secrets namespace, and each reads the other's
Connections and Variables.

Whether the two rows can coexist at all is decided by the database's collation
on a `String` primary key rather than by Airflow, so the same configuration
behaves differently across backends. Rejecting the collision at creation makes
the behaviour uniform and fails at the moment the name is chosen, rather than
silently merging two teams' secrets later.

Both creation paths are covered. `teams sync` checks the incoming names against
each other as well as against the stored ones, because a bundle config can
introduce both halves of a collision in the same run.

`upper()` rather than `casefold()`: it is what the backend applies, and team
names are restricted to ASCII by the name pattern.

Generated-by: Claude Opus 5 (1M context) following the guidelines at
https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions

Report URL: https://github.com/apache/airflow/actions/runs/30678095714

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to