-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move workflow to its own database/api #1204
Conversation
Why you want to move workflow package to the engine. It's rather a general name and also the name of main repo. |
We have now a model called We could go with I'm open for suggestions on the name for this package or just keep it as it is |
let's keep it like this for this PR and change it in a future PR.
|
Co-Authored-By: Nicolas Mahé <nicolas@mesg.com>
Another PR created for the renaming #1208 |
@antho1404 just to remind you you can use |
Dependency #1201
There is a lot of copy/paste from the existing service SDK/API. I didn't change the workflow engine, just moved it from
workflow
toengine
packageNow there is 4 new apis:
Workflow.Create
Workflow.Delete
Workflow.Get
Workflow.List
When we create the workflow, all the instances will be validated and once recorded in the database the workflow engine will start to process executions related to this workflow.
There is no need to deploy a service with no source code.