CLI tool & correctly stopping it?

[ringods]

I am designing a data migration tool. To perform migration and intermediate transformation steps, each could be very elegantly be implmented as an actor. But when all the data is migrated, how should/would I signal this to all the actors to stop and be able to return an exit code from my main function?

[halturin]

I would use Events for that https://docs.ergo.services/basics/events

PS I'm working on act.Saga now, which is intended specifically for such cases. It will be a part of 3.1 release.

[ringods]

What is the 3.1 timeframe?

[halturin]

~ April 2025

[ringods]

@halturin I will have a look at Events. But when I look at the examples, they all seem to end with a node.Wait(), for instance:

https://github.com/ergo-services/examples/blob/0cc99885eef07c013ab86d968e7bd123f608c745/call/demo.go#L54

How should I implement a grafeful exit, preferrably with the ability to return an exit code as most CLI's have.

[halturin]

Use Stop method of gen.Node interface https://docs.ergo.services/basics/node#node-shutdown

There is no way to specify exit code so far. Probably good to add it at some point.