Arsenii01/13/2021, 11:57 AM
as the `idempotency_key`" way of registering flows is very useful for CI pipelines, however it's not really viable if you have to spend a lot of time building
flow storage object before calling
. Can anyone please share a quick way of getting idempotency key for a specific flow name through GraphQL, if there is one? I am thinking of looping through all the available flows, and using the serialized hash to automatically filter out changed flows. Right now we are using a clunky
solution that basically does
on flow source files between tagged releases on a Github repo. Thank you.
Arsenii01/14/2021, 1:40 AM
and they mention that task code is not included in the serialized flow... Makes sense, the server does not need to know about that. So if the flow structure keeps exactly the same but there's a small tweak in a task, the change would not be detected -- this unfortunately does not play well with our CI process so I'll keep the git-based solution for now. Thanks again!