-
Bug
-
Resolution: Done
-
Major
-
3.12.0.GA
-
False
-
None
-
False
-
-
Description of problem:
this issue with PROJECTS_ROOT environment variable being set to '/projects/projects' started after we upgraded the Dev Spaces operator to version 3.12.
On Dev Spaces 3.11, PROJECTS_ROOT was set correctly as 'projects' in the VSCode editor once the workspace spun up.
this seems to be stemming from che plugin.
This is from workspace’s env vars, after che plugins are loaded:
## Extension: eclipse-che.api
- `DASHBOARD_URL=${env:DASHBOARD_URL}https://devspaces.apps.`
- `WORKSPACE_NAME=${env:WORKSPACE_NAME}ocp-admin`
- `WORKSPACE_NAMESPACE=${env:WORKSPACE_NAMESPACE}cr-ruslan`
- `PROJECTS_ROOT=${env:PROJECTS_ROOT}/projects`
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
Use Dev Spaces v3.12
Create Workspace from sample/custom devfile
Actual results:
PROJECTS_ROOT environment variable being set to '/projects/projects'
Expected results:
PROJECTS_ROOT environment variable set to '/projects'{}
Workaround:
Set 'PROJECTS_ROOT=/projects && export PROJECTS_ROOT'