Chapter 3. Bug fixes

Before this update, as a result of a bug, administrators were unable to enforce a list of containers to add to all workspaces. With this update, to automatically include specific containers in all workspaces in OpenShift Dev Spaces, administrators can specify a URI to a devfile defining a container component in devEnvironments.defaultPlugins of the CheCluster Custom Resource.

Before this update, starting a workspace from a branch of a Git repository with a slash (/) resulted in a "devfile could not be found" error. With this update, the issue is solved.

Before this fix, if an administrator customized some of the fields in the CheCluster Custom Resource (such as .spec.components.pluginRegistry.openVSXURL), the values could be overridden by the operator. With this update, the issue is fixed.

Before this update, developers could not add their Microsoft Azure DevOps Personal Access Token from the User Preferences menu in OpenShift Dev Spaces Dashboard. With this update, the issue is fixed.

Before this update, when a developer tried to authenticate with GitHub (for example to clone a repository or to use a GitHub extension) with an expired GitHub token or without a token, the operation could fail due to an authorization error. With this update, when no valid GitHub token is found, the user is informed how to generate it.

Before this update, when a developer started an empty workspace (not linked to a specific Git repository) or a OpenShift Dev Spaces sample, any consequent try to run git push would fail due to an authorization problem. This would occur even if the developer had pre-configured a personal access token for the Git service. With this update, pre-configured personal access tokens are mounted in empty workspaces and sample workspaces so that git push runs successfully.