question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Telemetry Plugin support in DevWorkspaces (workspaces started with the DevWorkspace engine)

See original GitHub issue

Is your task related to a problem? Please describe.

As part of this task, we need to make sure that the telemetry plugin that is possible to enable for Che 7 workspaces can be re-used, or need to be adapted, for the DevWorkspaces - https://www.eclipse.org/che/docs/che-7/extensions/telemetry/

Describe the solution you’d like

It should be possible to enable telemetry plugin for all DevWorkspaces running on a cluster. Currently, in Che 7 plugin the can be enabled via

spec:
  server:
    customCheProperties:
      CHE_WORKSPACE_DEVFILE_DEFAULT__EDITOR_PLUGINS: 'eclipse/che-machine-exec-plugin/7.32.0,https://your-web-server/meta.yaml'

Describe alternatives you’ve considered

N/A

Additional context

telemetry - https://www.eclipse.org/che/docs/che-7/extensions/telemetry/ Devfile v2 and IDE plug-ins - https://che.eclipseprojects.io/2021/06/23/@florent.benoit-devfile-v2-and-ide-plug-ins.html

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:18 (15 by maintainers)

github_iconTop GitHub Comments

2reactions
l0rdcommented, Nov 23, 2021

@ibuziuk I am ok with this approach but consider a couple of things:

  1. devWorkspace section in the CRD should disappear because everything will be devWorkspace
  2. The default plugins will depend on the editor, so maybe it would be better to specify the editor too

So maybe something like this may be better:

  server:
    workspacesDefaultPlugins:
      - editor: 'che-theia'
        plugins: ['github/vscode-pull-request-github/latest', ...]
      - editor: 'vscode'
        plugins: ...  
1reaction
amisevskcommented, Dec 6, 2021

For managing default plugin templates, we can do what the Web Terminal Operator does in order to avoid maintaining DWTs across the cluster. If we create DevWorkspaceTemplates in a known namespace (WTO uses its current namespace) and add the annotation

controller.devfile.io/allow-import-from: "*"

then these DWTs can be used in any workspace on the cluster via

spec:
  template:
    components:
      - name: my-default-plugin
        plugin:
          kubernetes:
            name: k8s-dwt-object-name
            namespace: k8s-dwt-namespace
Read more comments on GitHub >

github_iconTop Results From Across the Web

DevWorkspace Switch - Endgame Plan · Issue #20830
Telemetry. DONE Telemetry Plugin support in DevWorkspaces (workspaces started with the DevWorkspace engine) ...
Read more >
Red Hat OpenShift Dev Spaces 3.0 Administration guide
Specifying the telemetry plug-in in a DevWorkspace ... When the user requests the user dashboard to start a workspace, the user dashboard ...
Read more >
Web terminal | Web console | OpenShift Container Platform 4.10
To launch the web terminal, click the command line terminal icon ( odc wto icon ) · Select the project where the DevWorkspace...
Read more >
Devfile v2 and the DevWorkspace Operator - Part 1
With version 7.28 of Che we have introduced a new workspace engine, the DevWorkspace Operator, that supports v2 of the Devfile specification ...
Read more >
Introduction to Eclipse Che :: Eclipse Che Documentation
Contents. Getting started with Che; Joining the community; What is Eclipse Che; Workspace model; Browser-based IDEs; Extensible platform; Enterprise integration.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found