Fixed logic to give the correct AppWrapper status transition #577
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes have been made
When an AppWrapper has multiple generic items that finish at different times, transitioning to
Complete
state depends on the status conditions of each generic item. If no generic item has reached any of its specifiedcompletionstatus
conditions, then the AppWrapper remains inRunning
state after dispatching. If some but not all of the generic items reach theircompletionstatus
conditions, then the AppWrapper state becomesRunninHoldCompletion
. Once all the generic items reach theircompletionstatus
conditions, then the AppWrapper becomesCompleted
.Verification steps
To observe the transitions use the following AppWrapper and monitor the
.status.state
value for the AppWrapper as time goes by. Without these changes, the AppWrapper goes fromRunning
toCompleted
despite the fact that some generic items complete in between the two states. The correct transition should beRunning->RunningHoldCompletion->Completed
:Checks