I’m building an app that will be shipped as a binary and needs to emit events in its workflows.
Events in this case will mean executing activities. I want to use the app in multiple environments (preferably without compiling a version per environment), so my idea is to provide activity names and a bunch of other options as configuration to the workflow.
Something like this:
events: created: activities: - name: my-created-event-activity timeout: 20m failOnError: true - name: my-other-created-event-activity timeout: 10m failOnError: false
The workflow will read this configuration and execute the appropriate activities (in parallel? sequentially? this could also be configured?)
What do you think? Is there anything missing there? Are there any existing practices for such scenarios?