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

Give more flexibility on where devfile registry can served up #13634

Closed
makandre opened this issue Jun 26, 2019 · 14 comments
Closed

Give more flexibility on where devfile registry can served up #13634

makandre opened this issue Jun 26, 2019 · 14 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system.
Milestone

Comments

@makandre
Copy link

Description

I would like to make devfiles I have on GitHub show up in Che dashboard when creating a workspace.

I learned that I can configure Che's devfile registry by changing the che.workspace.devfile_registry_url property.

It would be great if I can change it so the devfiles can be served up directly from GitHub (e.g. set che.workspace.devfile_registry_url=https://raw.githubusercontent.com/kabanero-io/codewind-templates/master/)

But this doesn't work; Che takes the url and does a GET on <url>/devfiles/ to get the contents of the index.json (and obviously that won't work for GitHub). If it simply does a GET on <url>/devfiles/index.json instead, then I believe it would work. (it would be a small change here https://github.com/eclipse/che/blob/master/dashboard/src/components/api/devfile-registry.factory.ts#L46)

Reproduction Steps

OS and version:

Diagnostics:

@tobespc
Copy link
Contributor

tobespc commented Jun 27, 2019

I'm trying to get that to work by submitting a PR against che to pretty much suggest what you have said

@sleshchenko sleshchenko added the kind/enhancement A feature request - must adhere to the feature request template. label Jun 27, 2019
@rhopp rhopp added this to the 7.1.0 milestone Jul 10, 2019
@rhopp rhopp added the severity/P2 Has a minor but important impact to the usage or development of the system. label Jul 10, 2019
@rhopp rhopp modified the milestones: 7.1.0, 7.x Jul 10, 2019
@l0rd l0rd added the team/ide2 label Jul 10, 2019
@l0rd
Copy link
Contributor

l0rd commented Jul 12, 2019

Based on the PR discussion #13645 (comment) I would +1 to set milestone 7.0.0 and merge the PR
@nickboldt @tsmaeder @rhopp @slemeur

@nickboldt nickboldt modified the milestones: 7.x, 7.0.0 Jul 12, 2019
@nickboldt
Copy link
Contributor

+1, added to che7GA and milestone 7.0.0.

@makandre
Copy link
Author

Thank you!

@slemeur
Copy link
Contributor

slemeur commented Jul 16, 2019

@makandre : As the PR been merged, is this issue solved?

@makandre
Copy link
Author

Hi @slemeur, for my usage I'm packaging a custom assembly where I change the che.workspace.devfile_registry_url value to point to my repo with the index.json

So I have been using 7.0.0-RC-3.0-SNAPSHOT as the base che assembly, however it doesn't appear to contain the fix yet. Am I using the right version? Is there another version I should be using which contains the fix? Thanks.

@slemeur
Copy link
Contributor

slemeur commented Jul 16, 2019

Thanks for your answer @makandre !
The fix has been merged yesterday, so you should pull the latest snapshot of RC 3.
How and where are you deploying Che?

@l0rd l0rd mentioned this issue Jul 16, 2019
85 tasks
@makandre
Copy link
Author

I just built again with 7.0.0-RC-3.0-SNAPSHOT but it still does not have the fix

@makandre
Copy link
Author

Will there be 7.0.0-RC-4.0 images?

@amisevsk
Copy link
Contributor

I believe we are currently on 7.0.0-rc-4.0-SNAPSHOT, rc-3.0 was released a few weeks ago and is not taking current commits (I think @slemeur mistyped)

However, if all you are doing to modify the assembly is setting che.workspace.devfile_registry_url, this can be done in the current eclipse/che-server:nightly image by setting the environment variable

CHE_WORKSPACE_DEVFILE__REGISTRY__URL

in the container. Generally properties can be overriden at runtime via env vars using the translation '_' -> '__'; '.' -> '_'; toUppercase().

@tobespc
Copy link
Contributor

tobespc commented Jul 17, 2019

we have tested the master branch and can see it in there ok

@makandre
Copy link
Author

@amisevsk Thanks for the clarification. I'm able to verify it works now.

@amisevsk
Copy link
Contributor

@makandre No problem, happy to help! There's a little more information in an (old, but still valid) doc: https://www.eclipse.org/che/docs/che-6/properties.html#properties-and-environment-variables

@slemeur
Copy link
Contributor

slemeur commented Jul 18, 2019

Excellent! Thanks @amisevsk for following-up !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

9 participants