Abhishekmishra2808 commented on issue #62500:
URL: https://github.com/apache/airflow/issues/62500#issuecomment-4023904916
From the discussion, it seems the important distinction is that the **skill
layer should represent contributor workflows**, not just mirror the Breeze CLI
commands. In that sense, Breeze becomes an **execution mechanism for
reproducibility**, rather than the primary abstraction exposed to agents.So
instead of a CLI-driven model, the system would likely look like a
**workflow-driven execution model**, where the agent decides whether to run
locally or fall back to Breeze depending on context.
For example, a typical “run tests” workflow could follow something like:
```mermaid
flowchart TD
A[Code Change or PR Update] --> B[Run Static Checks]
B --> C{Static Checks Pass?}
C -- No --> D[Fix Lint or Formatting Issues]
D --> B
C -- Yes --> E[Run Tests Locally]
E --> F{Dependencies Available?}
F -- Yes --> G[Run Local Tests<br/>uv run --project distribution_folder
pytest]
F -- No --> H[Fallback to Breeze]
H --> I[Start Breeze Environment<br/>breeze shell or breeze exec]
I --> J[Run pytest inside container]
G --> K[Analyze Test Results]
J --> K
K --> L{Tests Pass?}
L -- No --> M[Fix Code or Tests]
M --> E
L -- Yes --> N[Ready for PR / CI Verification]
```
Conceptually the architecture could then look like:
```mermaid
flowchart LR
A[Contributing Guides] --> B[Workflow Definitions]
B --> C[Agent Skill Layer]
C --> D{Execution Strategy}
D --> E[Local Execution]
D --> F[Breeze Execution]
E --> G[Local Commands<br/>uv run pytest, prek, etc.]
F --> H[Breeze Commands<br/>breeze shell, breeze exec, airflow services]
```
In this model:
* **Contributing guides** act as the source of truth for workflows.
* **Agent skills** encode those workflows in a structured format.
* The **execution strategy layer** decides whether commands should run
locally or via Breeze.
* Breeze remains the **reproducibility fallback** when local execution is
insufficient (missing dependencies, CI mismatch, etc.).
One possible implication is that Breeze CLI metadata could still be used to
**derive or validate the Breeze execution layer**, while the workflow
abstraction remains aligned with the contributing documentation. right?
--
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]
