-
Notifications
You must be signed in to change notification settings - Fork 57
Implement compatibility with the new automatic multicast discovery in plugin broker #1354
Comments
Related to the Future Improvement comment in the merge meta.yaml / plugin.yaml change -eclipse-che/che#12908 (comment) |
It is important that we do not break self hosting as described in https://docs.google.com/document/d/1V292nYN655ekPPZvzdg7zbLpwVXW5uFjmffgoN2CmpM/edit#bookmark=id.kw179rb9gjl6 |
@benoitf any idea about whether it might break self-hosting ? |
@davidfestal why it should break self-hosting ? |
@benoitf https://docs.google.com/document/d/1V292nYN655ekPPZvzdg7zbLpwVXW5uFjmffgoN2CmpM/edit#heading=h.mu558mvq9pl4 suggests running the ide and plugin containers "by hand" in a workspace: if we can't tell the ide container where the plugin host is, how do we separate the outer editor (the one we're using to develop) from the inner (the one being developed)? |
@davidfestal @tsmaeder in fact multiple containers is still compliant with discovery (as we share the network). Moreover, there are custom ENV variables allowing to specify the discovery host/port if you need to opt-out |
@benoitf can we please try this work flow and document it in the referenced document before we turn on discovery as the default mechanism? IMO, we need to continuously improve developer experience and we should make sure at the very least that we don't break documented work flows. |
@davidfestal, as I understand once the docs are updated we can close this issue, right? |
Moving to Done. since it is merged to plugin-broker-master. Should be closed once plugin broker |
Placeholder for eclipse-che/che#13272
The text was updated successfully, but these errors were encountered: