-
Notifications
You must be signed in to change notification settings - Fork 28
Execution Workflow
David Klingenberg edited this page Apr 24, 2017
·
1 revision
- Create Migration Project
- Upload applications
- Configure Analysis
Now there are 2 options:
- Click "Save" button
- Request to AnalysisContext endpoint is initiated. It uses migration project id as parameter. AnalysisContext id is not being passed and it is impossible to update AnalysisContext by its id.
- Default AnalysisContext of project is updated (this is the only place where it can be changed)
- Click "Save & Run" button
- First, the same steps as in option 1) are executed
- After successful update, updated version of AnalysisContext entity is sent to Windup execution endpoint
- WindupExecution endpoint makes a clone of AnalysisContext object and uses it for given execution
- Cloned AnalysisContext object is bound with WindupExecution, which makes it immutable (it is even checked in code)
This workflow is here to guarantee AnalysisContext used for WindupExecution won't be ever modified.