Thanks to colleague Steve Adroulakis for providing inspiration and example for parsing Temporal Workflow history.
This python script will take a directory containing one or more Temporal Workflow histories and analyze each to provide further insight into how easy or difficult a given workflow is to migrate. It will also point out things that should be considered when migrating a workflow from one namespace to another (typically between self-hosted and cloud). The goal being to weed out the workflows that are easy to migrate with a drainable approach or those that require more discovery and thought.
Output is provided in csv format so it can be imported into excel.
$ python migration_advisor.py <Directory of JSON History Files>To run on example history files:
$ python migration_advisor.py example_historyOutput:
filename,workflowid,isLongRunning,isContinueAsNew,isSignal,isUpdate,isParent,isChild,isInputSearchAttribute,isUpsertSearchAttributes,catagorization
search_attributes_events.json,order-317711,False,False,False,False,False,False,False,True,simple
update_events.json,order-148643,False,False,False,True,False,False,False,False,complex
parent_events.json,order-153996,False,False,False,False,True,False,False,False,complex
three_signal_events.json,TRANSFER-VSV-155,False,False,True,False,False,False,False,False,complex
zero_signal_events.json,TRANSFER-SOQ-104,False,False,False,False,False,False,False,False,simple
one_signal_events.json,TRANSFER-BAX-210,False,False,True,False,False,False,False,False,complex
child_events.json,shipment-153996-654321,False,False,False,False,False,True,False,False,complex
continue-as-new_events.json,child_workflow:c4efae11-7b91-4c53-ac6c-64abb4ff70f7,False,True,False,False,False,True,False,False,complex