UI is broken for breeze kind-cluster deploy
#16939
Assignees
Labels
kind:bug
This is a clearly a bug
Comments
|
Yep. Very likely indeed! |
|
kind-cluster deploy builds prod image from sources rather than from package, so you are probably right that this change broke it! |
|
Hmm. But the "else" should handle it 🤔 |
|
Will take a look tomorrow! |
|
Thanks, Jarek. |
|
Ah yeah. due to summit, tomorrow took a bit long... But I am down to 100 messages to process. This one is on the list. |
|
Cool. Thanks!
|
potiuk
added a commit
to potiuk/airflow
that referenced
this issue
Jul 19, 2021
The apache#16577 change removed yarn.lock from installed packages and it removed the possibility of preparing assets after the package is installed - so far that was the way it was done in the PROD image built from sources. The asset compilation was supposed to work after the change but it was not performed in this case. The change fixes it by: * detecting properly if the PROD image is built from sources (INSTALLATION_METHOD) * compiling the assets from sources, not from package * installing airflow from sources AFTER assets were compiled Fixes apache#16939
potiuk
added a commit
that referenced
this issue
Jul 19, 2021
The #16577 change removed yarn.lock from installed packages and it removed the possibility of preparing assets after the package is installed - so far that was the way it was done in the PROD image built from sources. The asset compilation was supposed to work after the change but it was not performed in this case. The change fixes it by: * detecting properly if the PROD image is built from sources (INSTALLATION_METHOD) * compiling the assets from sources, not from package * installing airflow from sources AFTER assets were compiled Fixes #16939
potiuk
added a commit
to potiuk/airflow
that referenced
this issue
Aug 2, 2021
…e#17086) The apache#16577 change removed yarn.lock from installed packages and it removed the possibility of preparing assets after the package is installed - so far that was the way it was done in the PROD image built from sources. The asset compilation was supposed to work after the change but it was not performed in this case. The change fixes it by: * detecting properly if the PROD image is built from sources (INSTALLATION_METHOD) * compiling the assets from sources, not from package * installing airflow from sources AFTER assets were compiled Fixes apache#16939 (cherry picked from commit 660027f)
tzanko-matev
pushed a commit
to santiment/airflow
that referenced
this issue
Aug 17, 2021
…e#17086) The apache#16577 change removed yarn.lock from installed packages and it removed the possibility of preparing assets after the package is installed - so far that was the way it was done in the PROD image built from sources. The asset compilation was supposed to work after the change but it was not performed in this case. The change fixes it by: * detecting properly if the PROD image is built from sources (INSTALLATION_METHOD) * compiling the assets from sources, not from package * installing airflow from sources AFTER assets were compiled Fixes apache#16939
kaxil
pushed a commit
that referenced
this issue
Aug 17, 2021
The #16577 change removed yarn.lock from installed packages and it removed the possibility of preparing assets after the package is installed - so far that was the way it was done in the PROD image built from sources. The asset compilation was supposed to work after the change but it was not performed in this case. The change fixes it by: * detecting properly if the PROD image is built from sources (INSTALLATION_METHOD) * compiling the assets from sources, not from package * installing airflow from sources AFTER assets were compiled Fixes #16939 (cherry picked from commit 660027f)
jhtimmins
pushed a commit
that referenced
this issue
Aug 17, 2021
The #16577 change removed yarn.lock from installed packages and it removed the possibility of preparing assets after the package is installed - so far that was the way it was done in the PROD image built from sources. The asset compilation was supposed to work after the change but it was not performed in this case. The change fixes it by: * detecting properly if the PROD image is built from sources (INSTALLATION_METHOD) * compiling the assets from sources, not from package * installing airflow from sources AFTER assets were compiled Fixes #16939 (cherry picked from commit 660027f)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using
breeze kind-cluster deployto deploy airflow in Kubernetes cluster for development results in unusable UIApache Airflow version: main
How to reproduce it:
Start kind cluster with
./breeze kind-cluster startDeploy airflow with
./breeze kind-cluster deployCheck the UI and see that it's broken:
Anything else we need to know:
This is likely as a result of #16577
The text was updated successfully, but these errors were encountered: