-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Plugin Broker should support relative paths #14163
Comments
will this change work for icons (.svg files) and theia extension (.theia files) too ? Need that as well as .vsix files for the air gap / offline / plugin-registry-all-in-one container solution planned for CRW 2.0 |
It should be workable for |
if this is a hard target of 7.1.0 I'd raise it to P1 or even blocker. "enhancement" sounds like "when I have time and all my P0, P1, and P2 work is done and my doc updates are done and I still have time left in the sprint" ... or am I reading too much into a label? :D |
@nickboldt Currently the plan is to pull it into our next sprint, it'll probably be the first thing I work on ;) |
@amisevsk can we close this one ? |
Yep, closing as fixed by eclipse-che/che-plugin-broker#70 and #14329 |
Is your enhancement related to a problem? Please describe.
To support offline plugin brokering, it's necessary for the plugin registry to know its own route. Since extension urls are set at build time, caching extensions locally within the registry (or elsewhere on the cluster) would require updating every
meta.yaml
's extensions field at startup.Describe the solution you'd like
The Che plugin broker currently supports downloading extensions via URL or reference to a vscode extension.
To support #14115, the broker should also support relative links. E.g. the reference:
would resolve to
${CHE_WORKSPACE_PLUGIN__REGISTRY__URL}/path/to/resource.vsix
.This would avoid having to update links at runtime in the offline case.
Describe alternatives you've considered
The main alternative is as suggested in #14115:
Additional context
This shouldn't be very difficult to implement, so even if it's a temporary solution I think it's important.
The text was updated successfully, but these errors were encountered: