-
Task
-
Resolution: Unresolved
-
Major
-
3.7.0.GA
-
productization: build & internals, Team A: Dashboard, devfile and plugin registries, open-vsx, operator + chectl/dsc, devfile-converter, configbump + traefik, image-puller, server, gateway, authentication, try-in-web-ide action, telemetry, Team B: DevWorkspace + Operator, Web Terminal + Operator, editors/IDEs + built-in vscode extensions, Universal Developer Image, machine-exec, dev environment config
-
None
-
False
-
None
-
False
-
-
Today we cache a copy of yarn v1 in https://github.com/redhat-developer/devspaces-images/tree/devspaces-3-rhel-8/devspaces-dashboard/.yarn/releases
But if configuration is broken in job-config.json, this file an be trashed and replaced by a nulled file:
https://github.com/redhat-developer/devspaces-images/commit/fa95aea671b4b6987daf2a5349dd32285107108d
This also introduces a dependency from traefik, devfile reg and others onto this file.
Instead we should use the same sync.sh logic in https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-8/devspaces-dashboard/build/scripts/sync.sh#L85-L92 for other repos, and then use the binary for that project in mid and downstream builds.
Yes it duplicates content, but it decouples the dependency on dashboard.