Haha Me again! So I am having some trouble with attaching

Result

classes to my flows. If I specify the result class in the same file that the flow is defined via

flow.result = ...

everything works as expected. However if I import the flow def and then attach the result class (same way just outside the flow def) I do not get any stored results. I have put together a minimal repo here -> https://github.com/josh-gree2/minimal-repo/compare/result-in-cli...master (the two branches show what I mean)

I must say, this is weird.

Are you able to reproduce?

I haven't tried to yet. Just trusting your example 😄

Could it be to do with the way I am renaming the flow object in the

__init__.py

perhaps?

Not afaik

The reason this is important for me is because I need to be able to easily switch between local dev (docker run config, local results with a mount) and production deploy (k8s run config, GCS result) - I deal with the differences within a cli which attaches the desired run config and result storage at registration time

So this looks like it arises because the

result

is not serialized in the Flow object, so the result type attached to a flow is loaded when the flow is loaded from storage

Ok so when it's "Loaded from Storage" in my case this is the flow as it appears in the flow def file (without the storage class attached) because I use module storage? So can I mitigate in anyway?

You'll have to set the result in the flow def file, a possible work around is to add an environment variable to your run config and use that to dynamically set the result in your flow

Ahh ok yeah that could work - will give it a try

Yep

Much thanks! Will keep an eye on that issue - it should behave as I expected yeah?

I'm not sure. It may be because we support custom result types which we can't serialize.