Skip to content
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.

Expose che-plugin-registry publicly to allow access from Che UD #807

Closed
5 tasks
garagatyi opened this issue Aug 20, 2018 · 1 comment
Closed
5 tasks

Expose che-plugin-registry publicly to allow access from Che UD #807

garagatyi opened this issue Aug 20, 2018 · 1 comment
Milestone
Sprint #154

Comments

@garagatyi
Copy link

Issue problem:

Now che-plugin-registry is not accessible for UD on OSIO prod-preview, but we will need that for Eclipse Con epic eclipse-che/che#10644

Red Hat Che version:

version: (help/about menu)

  • I can reproduce it on latest official image

Reproduction Steps:

Describe how to reproduce the problem

Runtime:

runtime used:

  • minishift (include output of minishift version)
  • OpenShift.io
  • Openshift Container Platform (include output of oc version)
  • k8s (include output of kubectl version)
@ibuziuk ibuziuk added this to the Sprint #154 milestone Aug 22, 2018
@l0rd l0rd mentioned this issue Aug 30, 2018
Closed
57 tasks
@benoitf benoitf changed the title Expose che-plugin-regisrty publicly to allow access from Che UD Expose che-plugin-registry publicly to allow access from Che UD Sep 4, 2018
@ibuziuk
Copy link
Member

ibuziuk commented Sep 7, 2018

This one is fixed now - there are routes exposed to che-plugin-registry from both prod / prod-preview

@ibuziuk ibuziuk closed this as completed Sep 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Sprint #154
Development

No branches or pull requests
2 participants
@ibuziuk @garagatyi