Devmode service tags

If you have a system with many microservices, you might not necessarily want to run them all at once, instead you might want to run just a group of microservices. This could be supported by allowing services to be tagged with sequence of tags, configured in build.sbt, and then having the runAll command be an input task that takes a tag, allowing you to run only the services with that tag if specified.

Additionally, we might want to be able to configure other things about the build environment based on which tag is selected, for example, whether Kafka, Cassandra, or the service locator are started, and also what external services should be added (for example, you may have a tag that, instead of starting service X, adds an external service URL to a shared development instance of service X).

[JurajBurian]

In sbt case, Is there any chance to reuse bgRun?, Then one can use: ; service1/bgRun; service2/bgRun … . After some research I realized, that one can run subset of services via lagomRun. Also one can run services in several rounds, because call of lagomRun execution returns promt to sbt when service execution is finished.

[TimMoore]

I think we should provide the feature for both sbt and Maven, but it doesn’t have to be identical for each. It should be idiomatic to each tool. I think it’s fine for the sbt plugin to support more-powerful features of sbt that Maven doesn’t provide, as long as we don’t just ignore Maven.