peerdb
peerdb copied to clipboard
MultiQRepFlow
dogfooding by using for SnapshotFlow
TODO:
- [ ] tests
- [ ] manual testing with xmin
- [ ] creating route and handler
- [ ] UI (in a future PR)
- [ ] find a way to continue as new to prevent history too large
- [ ] figure out catalog for child workflows
is this a breaking change?
is this a breaking change?
so far it shouldn't be, but while implementing route and UI might have to change existing protos in the future we can remove the workflow indirection and directly call activities from MultiQRepWorkflow
not a priority as of now, can revisit later