-
Notifications
You must be signed in to change notification settings - Fork 150
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: Embed OpenVsx in plug-in registry with few vsix files #1324
Conversation
Skipping CI for Draft Pull Request. |
@benoitf: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
2 similar comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@benoitf it seems openshift-ci built is failed because it uses rhel.entrypoint.sh that was removed |
@svor ok 👍 |
@svor it looks like tests have their own Dockerfiles so it looks odd to test stuff using their own copy/fork of the project's Dockerfiles |
@benoitf I agree openshift.ci tests look odd, they should be reworked for sure. But maybe in another PR, without this check we can't merge current PR. |
1 similar comment
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: benoitf, svor 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 |
@benoitf I was not able to test it. I see that open-vsx starts successfully in the plugin registry container but then neither Theia/VSCode are consuming it. Is there a particular Che Theia image that I should use? And if I want to try it with Che code should this work?
|
CheTheia is not consuming at all OpenVSX (it's still consuming the plugin registry as before) So basically, there is no change if you're still using CheTheia but you can look at the 'how to test' section of this PR and try the registry with some Desktop tool (like VSCodium, etc) and for VSCode, yes if you edit the DevWorkspaceTemplate to use a new image, when workspace will start it'll use the new registry. |
you can also look at |
I tried to test yesterday but I had issues with the plugin registry first: After patching the CheCluster (I did that after the installation) the new plugin registry Pod failed to start
I changed the memory limit to 1800Mi and the plugin registry started successfully. But then the dashboard started to be unresponsive: In the logs I got "Unexpected error null"
I have tried to reinstall Che but the dashboard was still not working. I am retrying today. |
And as discussed we should introduce a check of the variable I have created a separate issue for the opererator to set this variable to |
New changes are detected. LGTM label has been removed. |
Added a fixup for |
I was able to move a little bit forward. Although I couldn't test with Anyway I still faced the memory problem: Based on that I would recommend a more robust memory setup done by che-operator:
Note to self: to test with che-code of che-code PR #85 use
|
Change-Id: I6b42aa61a6d6b8077441fab270d6950954e29698 Signed-off-by: Florent Benoit <fbenoit@redhat.com>
Change-Id: I5ce218802e2f17453b3cc4f1f0ccdde12914eb8b Signed-off-by: Florent Benoit <fbenoit@redhat.com>
merging as now che-operator should default to open-vsx.org and then it means the local OpenVSX instance is not started |
What does this PR do?
Include OpenVSX in the plug-in registry
It will include some vsix coming from the
openvsx-sync.json
file (like 5 extensions for now)Screenshot/screencast of this PR
What issues does this PR fix or reference?
eclipse-che/che#20549
How to test this PR?
Build the image (or use my image) and then starts Che using that image:
example:
chectl server:deploy --platform=... --che-operator-cr-patch-yaml=...patch-pluginregistry.yaml
with cr patch beingyou should be able to use it by using CheTheia (which consume the plugin-registry API)
Then, for example by using VS Codium or another instance, edit the product.json of the app to point to the instance of this openvsx instance
For example on macOS, edit
./Contents/Resources/app/product.json
from/Applications/VSCodium.app
folderby updating content to
(using your correct nip.io/location)
Then, reset file permissions
xattr -r -d com.apple.quarantine /Applications/VSCodium.app
Make sure the Che CaCert certificate is trusted on your mac, (import the file generated by
chectl cacert:export
command)and then if you go in
extensions
page on VSCodium you should see the few listinstallation should also work (for example
redhat.vscode-yaml
extension)PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.
Change-Id: I6b42aa61a6d6b8077441fab270d6950954e29698
Signed-off-by: Florent Benoit fbenoit@redhat.com