Support tunnels conflicting across workshops

[Saviq]

Trying to launch a workshop that exposes a HTTP port, when another workshop already exposes it:

$ workshop launch
error: cannot perform the following tasks:
- Setup "system" SDK profile (The following instances failed updating (profile change still saved):
 - Project: workshop.michal, Instance: dev-60bb71a8: Failed starting device "system_doc": Error occurred when starting proxy device: Error: Failed listening on 127.0.0.1:8000: listen tcp 127.0.0.1:8000: bind: address already in use

Workshop should deal with that since it has the context. Probably launch without auto-connecting the interface.

workshop connect … could then ask whether to disconnect the offending connection.

It should also be possible to redirect the tunnel to another endpoint?

[jonathan-conder]

We have a planned feature called workshop notices which will replace workshop warnings. With this, failure to auto-connect will result in a notice rather than a hard error.

It should also be possible to redirect the tunnel to another endpoint?

I had a rough idea for a workshop forward command to dynamically adjust ports, similar to workshop remount. We may add something like that but it hasn't been designed yet, no timeline on that one.

[dmitry-lyfar]

I think not connecting it, raising a warning that advises to disconnect a conflicting connection and moving on sounds like a good idea and, presumably, not so hard to implement. It can then be channeled through notices.