Is your feature request related to a problem? Please describe
Hey guys, we’re currently using a custom in-house solution for declaring workflows as JSON, but we’re looking to replace this and Zigflow seems like the perfect fit.
We're looking at using Zigflow in production but there's one key Temporal feature that's not supported - context propagators. We’re currently using these to pass a tenant ID throughout a workflow, but in order to adopt Zigflow we need support for these.
In our current setup, the tenant is passed as a part of the workflow execution input and then set as part of the workflow context at runtime, which is then used in downstream activities and child workflows.
Hopefully I think this should fit within the scope of this project as it’s a standard feature within Temporal, but let me know if it's not and we can consider alternatives.
https://docs.temporal.io/encyclopedia/context-propagation
Is your feature request related to a problem? Please describe
Hey guys, we’re currently using a custom in-house solution for declaring workflows as JSON, but we’re looking to replace this and Zigflow seems like the perfect fit.
We're looking at using Zigflow in production but there's one key Temporal feature that's not supported - context propagators. We’re currently using these to pass a tenant ID throughout a workflow, but in order to adopt Zigflow we need support for these.
In our current setup, the tenant is passed as a part of the workflow execution input and then set as part of the workflow context at runtime, which is then used in downstream activities and child workflows.
Hopefully I think this should fit within the scope of this project as it’s a standard feature within Temporal, but let me know if it's not and we can consider alternatives.
https://docs.temporal.io/encyclopedia/context-propagation