Eclipse Che 7.50.0

Major Enhancements

Simplify Eclipse Che configuration format (CheCluster API v2)

CheCluster Custom Resource Definition has been updated to reflect that changes introduced with the switch to the DevWorkspaces. The result is a shorter and simpler configuration file to maintain for Eclipse Che administrators.

When a workspace is idled for inactivity user is redirected to Che dashboard

When a workspace is stopped after an inactivity now the users are redirected to the Dashboard. Previously a 503 error was displayed.

Allow an admin to specify Che default editor and containers

Che administrators can now configure the default editor (Theia, VS Code, IntelliJ or PyCharm) and the default container. Those defaults are used when the developer doesn't specify an editor or doesn't specify a devfile. The configuration can be done in the CheCluster Custom Resource in the the workspaces section using the just introduced defaultComponent and defaultEditor fields.

JetBrains IDEs running in a Che workspace autodetects the URL of a running application

As Visual Studio Code and Theia, now IntelliJ and PyCharm can detect when an application running in a Che workspace is listening to a given port and prompt the user to open the application URL. This is true even if the application has not been specified as an endpoint in the Devfile: a generic endpoint is assigned to applications that doesn't have a dedicated one.

oAuth-proxy enhancements for Azure AKS deployments

Some enhancements needed to deploy Che on Azure AKS has been contributed by @karatkep. Thank you for your contribution.

Major Bug Fixes

When using Visual Studio Code as a Che editor, the lines in the terminal are truncated and overlap

In VS Code terminal lines are not truncated anymore.