YusefSyed opened a new pull request, #72461:
URL: https://github.com/apache/airflow/pull/72461

   Closes #72265.
   
   ## Why
   
   The Kubernetes task source-rewrite and YAML deletion utilities had no direct 
tests. A regression could silently corrupt generated task code, select the 
wrong Kubernetes API method, or change deletion error handling without the 
project-structure gate noticing the behavior change.
   
   ## What changed
   
   - Cover task decorators with no arguments, arguments, nested parentheses, 
setup and teardown decorators, and absent task decorators.
   - Cover script rendering, native Jinja rendering, and strict missing-context 
behavior.
   - Cover Kubernetes API class derivation for core, named, `.k8s.io`, and 
multi-label DNS groups.
   - Cover CamelCase method conversion, namespaced and cluster-scoped dispatch, 
namespace precedence, List expansion, inherited API versions, and aggregated 
`ApiException` formatting.
   - Remove the two matching entries from `OVERLOOKED_TESTS`.
   
   ## Verification
   
   - Direct combined provider tests: 14 passed.
   - `airflow-core/tests/unit/always/test_project_structure.py`: 10 passed, 1 
expected xfail.
   - Applicable Ruff, mypy, license, test-location, and pre-commit checks: 
passed.
   - The two requested Breeze commands were attempted, but the local Docker 
CI-image build ended before producing a test result. No Breeze success is 
claimed. Hosted CI is the remaining environment-level verification.
   
   ## AI assistance
   
   Generative AI tools assisted with repository navigation, test drafting, 
command execution, and an independent diff review. I reviewed and approved the 
final three-file test-only change and understand the source-rewrite, Kubernetes 
dispatch, namespace, List, and error-aggregation cases it covers.
   


-- 
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]

Reply via email to