Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add che-code-server editor #1958

Merged

Conversation

vitaliy-guliy
Copy link
Contributor

@vitaliy-guliy vitaliy-guliy commented Feb 3, 2025

What does this PR do?

Adds new che-code-server editor that injects Visual Studio Code Command Line Interface (CLI) to the workspace, performs authentication and then creates a tunnel.

Screenshot/screencast of this PR

  • Login

Screenshot from 2025-02-03 21-38-09

  • Create tunnel to access the workspace

Screenshot from 2025-02-03 21-38-27

  • Open Visual Studio Code desktop

Screenshot from 2025-02-03 21-47-35

What issues does this PR fix or reference?

eclipse-che/che#23312

How to test this PR?

PR Checklist

As the author of this Pull Request I made sure that:

Reviewers

Reviewers, please comment how you tested the PR when approving it.

Copy link

openshift-ci bot commented Feb 3, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link
Member

@ibuziuk ibuziuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you need to run the following command - https://github.com/eclipse-che/che-operator?tab=readme-ov-file#update-development-resources
can be done from the dogfooding cluster

# Red Hat, Inc. - initial API and implementation
#

schemaVersion: 2.2.2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we use 2.3.0 ?

Copy link
Contributor Author

@vitaliy-guliy vitaliy-guliy Feb 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At the moment every editor definition use 2.2.2.
What if we update the version for all editors in the next pull request?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would update it in this PR, but up-to-you

metadata:
name: che-code-server
displayName: Visual Studio Code Server
description: Visual Studio Code server for Eclipse Che - latest
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to mention Eclipse Che here? would there be more follow up with downstreaming?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have to add a separate editor definition for downstream

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eclipse Che is mentioned in every editor definition.
It is not a problem to remove it, but then I suppose we have to update all the definitions.

Copy link

openshift-ci bot commented Feb 5, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tolusha, vitaliy-guliy

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@vitaliy-guliy
Copy link
Contributor Author

I think you need to run the following command - https://github.com/eclipse-che/che-operator?tab=readme-ov-file#update-development-resources can be done from the dogfooding cluster

There is written that we have to update the resources if we change any file in config directory or api/v2/checluster_types.go file.

You have to update development resources if you updated any files in config folder or api/v2/checluster_types.go file.

@ibuziuk
Copy link
Member

ibuziuk commented Feb 5, 2025

@tolusha do you know why the PR checks are failing?

@openshift-ci openshift-ci bot removed the lgtm label Feb 5, 2025
Copy link

openshift-ci bot commented Feb 5, 2025

New changes are detected. LGTM label has been removed.

@vitaliy-guliy vitaliy-guliy merged commit 2bb2eb1 into eclipse-che:main Feb 5, 2025
18 checks passed
@vitaliy-guliy vitaliy-guliy deleted the che-code-server-editor branch February 5, 2025 15:34
@devspacesbuild
Copy link

Build 3.19 :: operator_3.x/439: Console, Changes, Git Data

@devspacesbuild
Copy link

Build 3.19 :: get-sources-rhpkg-container-build_3.x/8837: FAILURE

devspaces-operator-bundle : 3.x :: Failed in 66589130 : BREW:BUILD/STATUS:UNKNOWN
FAILURE:; copied to quay

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

Build 3.19 :: get-sources-rhpkg-container-build_3.x/8838: FAILURE

devspaces-operator-bundle : 3.x :: Failed in 66591406 : BREW:BUILD/STATUS:UNKNOWN
FAILURE:; copied to quay

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

Build 3.19 :: get-sources-rhpkg-container-build_3.x/8839: FAILURE

devspaces-operator-bundle : 3.x :: Failed in 66593815 : BREW:BUILD/STATUS:UNKNOWN
FAILURE:; copied to quay

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

Build 3.19 :: get-sources-rhpkg-container-build_3.x/8840: FAILURE

devspaces-operator-bundle : 3.x :: Failed in 66595483 : BREW:BUILD/STATUS:UNKNOWN
FAILURE:; copied to quay

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

Build 3.20 :: get-sources-rhpkg-container-build_3.x/8844: FAILURE

devspaces-operator-bundle : 3.x :: Failed in 66597406 : BREW:BUILD/STATUS:UNKNOWN
FAILURE:; copied to quay

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

Build 3.20 :: get-sources-rhpkg-container-build_3.x/8846: FAILURE

devspaces-operator-bundle : 3.x :: Failed in 66597577 : BREW:BUILD/STATUS:UNKNOWN
FAILURE:; copied to quay

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

Build 3.20 :: get-sources-rhpkg-container-build_3.x/8847: FAILURE

devspaces-operator-bundle : 3.x :: Failed in 66598280 : BREW:BUILD/STATUS:UNKNOWN
FAILURE:; copied to quay

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

@devspacesbuild
Copy link

Build 3.20 :: get-sources-rhpkg-container-build_3.x/8848: FAILURE

devspaces-operator-bundle : 3.x :: Failed in 66599546 : BREW:BUILD/STATUS:UNKNOWN
FAILURE:; copied to quay

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
made-with-che Changes were made using Che
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants