The develop command doesn't obey service dependencies

[tanuck]

If service A depends_on service B in your compose file (i.e. a app service depends_on db service) and you then run navy develop on service A, the dependency will be ignored. I haven't looked into why yet.

@madjam002 was this the intended behaviour?

[tanuck]

So I found the culprit https://github.com/momentumft/navy/blob/master/packages/navy/src/cli/develop.js#L59

Would seem this is intentional.

[tanuck]

@madjam002 do you remember why you implemented it this way?

[madjam002]

@tanuck What's the use case here? Why (in your example above) do you need the db service to relaunch in the event of you developing an app service?

[tanuck]

Don't want it to relaunch... the problem is if it isn't running when you navy develop your service. I.e do the following:

1. navy kill
2. navy ps returns zero running services
3. navy develop your app service - now the depended upon service isn't running for your app service

[madjam002]

Ah yeah fair enough. The main reason nodeps was added is because sometimes developing a service which was heavily depended upon would cause like ~10 services to relaunch which sometimes takes quite a while.

[ThomWright]

So nodeps is really useful especially for running single-service tests, but it should probably default to false in every case, rather than sometimes true, sometimes false.

[madjam002]

Sounds good. Maybe it's a good idea to try changing the default in a beta or behind a feature flag to trial it?