Workflow Versioning #82
Open
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.
In light of the discussion around variations of workflow re-runs and the community ask for versioning, I wanted to introduce a new proposal that marries @JoshVanL 's Rerun from Activity proposal to a versioning migration scheme that addresses the issue I raised in one of the comments regarding base type inconsistency in running ad-hoc workflows against versioned underlying types.
I've gone through a couple iterations of this with others and this is the most recent version of the idea. Because the runtime isn't familiar with the type implementations of the workflows themselves in the application, this instead leans more on minor state changes on the workflow actor and changes to workflow resolution at the SDKs themselves than the runtime. At some point, following some feedback on this, I'd like to move ahead with a POC to prove out the concept, but I wanted to toss it out there first to see if I'm missing anything really obvious.
I've written this proposal assuming that we're wanting to move forward with both the Multi-App Workflows and the Rerun from Activity proposals to accommodate both in a way that enables all three concepts.
Thank you for the consideration!