Workflow stage dedup

[RemindD]

In my opinion, the same stage for an activation should only be executed once.
However, there could be situations that the trigger event for the next stage is published but the trigger event for the current stage fails which could makes the trigger events for the next stage published twice. So we need a way to identity whether the stage has been processed and skip duplication.
A single idea is to track a number for stage index in an activation. And when saving stage status in stageHistory, symphony will check if a stage is already running or ran.

[msftcoderdjw]

Why don't we avoid publish trigger event when current stage failed?

https://github.com/eclipse-symphony/symphony/blob/a32f89cd325b31f68db2be44feeddcc5123c14bb/api/pkg/apis/v1alpha1/vendors/stage-vendor.go#L198C1-L210C5

[msftcoderdjw]

@RemindD , let's discuss in details after you come back.

[RemindD]

• In current workflow, trigger event will
  1. persist running stage history in activation status
  2. run stage provider
  3. persist terminated stage history in activation status
  4. publish trigger event for the next stage if needed.
• Add an index in the stageSpec as well as activationData indicating the number of the stage in the activation running history
  • used for stage dedup
  • used for indication of stage history truncation
• Check the latest record in the stage history when persist stage history
  • If the latest record with a higher index, return badrequest
  • If the latest record with the same index, check if the status in stage history is running or terminated. If terminated, return badrequest as well.