jason810496 opened a new pull request, #59778: URL: https://github.com/apache/airflow/pull/59778
related: #57219 ## Why After [Auto-compile UI assets on Breeze start-airflow command #57219](https://github.com/apache/airflow/pull/57219), we could `breeze start-airflow --use-airflow version <pr-number> / <owner/repo:branch>` and access the Frontend successfully. We make it happen by: 1. download `node.js` 2. download `npm` 3. download `pnpm` 4. download repo as tarball from GitHub and extract it 5. run `pnpm build` 6. copy artifact to `/usr/python/lib/python3.10/site-packages/airflow/ui/dist` However, if we just want to test the Airflow Core change from someone's PR (e.g. validate API Server TaskInstance Log reading path, check Scheduler behavior but still want to access Frontend for observability, etc), we still need to do the all the steps above just to access Frontend, which is waste of time for test iteration. Instead, we could just **mount the pre-built UI dist from host to Breeze container to save the time**, in most of the time, the core change will not impact API Server <-> Frontend behavior. (e.g. When I testing [Fix rendering of template fields with start from trigger#55068](https://github.com/apache/airflow/pull/55068) recently, there isn't anything related with Frontend, but I still need to access it to check the TaskInstance status. ) ## What Add `--mount-ui-dist` flag for `start-airflow` command to mount UI dist directly from host to Breeze container without building the whole frontend again to save time. -- 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]
