Open bacongobbler opened 7 years ago
I was hoping we didn't have to specify --link
in this feature.
draft connect [app1] [app2]
feels intuitive. This should give us a local tunnel for each application and create a Kubernetes service for these two apps to speak to each other. Thoughts?
Update: currently spiking this feature and we may just want to have a discussion around this after a PoC demo.
Indeed that does looks like a good UI, though I could imagine we would want to extend the usage to draft connect [myapp] [appnames...]
so that a user can specify a number of deployed applications, all of which will be linked to app1 (e.g. I want a single microservice connected to all of my other microservices so it works).
a PoC would be great :)
I'll tackle this issue with everyone. :-) Formulating how this might work properly.
Right now it's possible to link two applications together if
But what if we could make that link implicit by creating those services for the user e.g.
draft connect --link=application-b[:alias]
, similar todocker run --link
?