omkhar opened a new pull request, #66718: URL: https://github.com/apache/airflow/pull/66718
The current `WorkerQueuesBase.team_name` field description implies the field provides team isolation when set. `workload.rst` documents the actual contract: `[core] multi_team` is experimental, and the Execution API does not enforce team boundaries today. This PR aligns the field description with that documented stance so operators reading only the API datamodel see the same caveats `workload.rst` already states. No behavior change. No new APIs. Docs / docstring only. **Before:** ``` Team name for multi-team setups. If not provided, worker operates without team isolation. ``` **After:** ``` Team name for the experimental ``[core] multi_team`` feature. This is a UI/REST API-level hint; the Execution API does not currently enforce team-based access boundaries -- see ``airflow-core/docs/security/workload.rst`` (section: 'No team-level isolation in Execution API'). Workers without team_name behave as default-team workers. ``` Cross-reference: `airflow-core/docs/security/workload.rst` section "No team-level isolation in Execution API (experimental multi-team feature)". -- 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]
