[CRW-3369] [BitBucket]che-editor.yaml overrides don't work - Red Hat Issue Tracker

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 3.5.0.GA, 3.6.0.GA
Affects Version/s: 2.15.4.GA, 3.1.0.GA
Component/s: controller: dashboard, factory/dashboard, ts-workspace-client, plugins: registries, factories, git
Labels:
- cee_medium

Blocked:
False
Blocked Reason:
None
Ready:
False
Steps to Reproduce:

Hide

Make a git repo that contains a devfile in BitBucket.
Start a workspace.
Using the OCP console, visit the Deployment and take a note of the resource limits for the workspace containers.

Stop the workspace, delete it.

Visit the git repo used for the workspace. Add a .che/che-editor.yaml file as seen in the docs. Assign a different memoryLimit.
Restart the workspace.
Note that the OCP console does not show a different memoryLimit.

Show
Make a git repo that contains a devfile in BitBucket. Start a workspace. Using the OCP console, visit the Deployment and take a note of the resource limits for the workspace containers. Stop the workspace, delete it. Visit the git repo used for the workspace. Add a .che/che-editor.yaml file as seen in the docs. Assign a different memoryLimit. Restart the workspace. Note that the OCP console does not show a different memoryLimit.

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

The documentation [1] includes section 5.2.3. (Using a custom plug-in registry for your IDE) and others that hint that using .che/che-editor.yaml can allow the user to influence things like memory limits. This does not seem to be true.

[1] https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.1/html-single/user_guide/index#using-a-custom-plug-in-registry-for-your-ide