Hey @Kevin Su! I'm looking for some way for agents to return metadata, to be stored inside the Flyte execution. I'm familiar with

ResourceMeta

returned from

CreateTask

- but it looks like that's intended to be a totally opaque byte stream strictly for using as a key that only the agent can understand. It doesn't look like there's a way inside Flyte to deserialize that for human consumption? Any thoughts on this? I see that the GetTaskResponse has a

custom_info

field in the proto , but it's not part of the Resource in the Python base agent ... only

outputs

,

log_links

,

message

and

phase

are there. Thanks!

Metadata should not be stored in propeller state

Thanks - yeah, I wouldn't expect the operator to do that kind of state management. Basically I'd just like a way to store some basic info about the execution the agent triggered in the remote system -- a simple hash would suffice.

@Ethan Brown you can send it today in https://github.com/flyteorg/flyte/blob/ee6037bfdb9498197baef48f4098a16d3a1bdb34/flyteidl/protos/flyteidl/admin/agent.proto#L140

Yeah that's the field I was saying doesn't look to be wired up in the Python agent resource helper class. I wasn't sure if that was intentional or not

That should be super simple

Just to follow up - put up a quick PR on this at https://github.com/flyteorg/flytekit/pull/2426. Will try to test it in conjunction with our agent later today / tomorrow.