https://flyte.org logo
Join Slack
Powered by
Hey team, we are trying to identify a user selecte...
# flyte-support
l
Hey team, we are trying to identify a user selected task in flyte remote client if they apply some decorated we created. One way to do it is to inject a tag in the task metadata in our decorator. However, after looking around, I can see there's a metadata 
tags
field under task 
metadata
section in our flyte console, but I don't seem to find any code reference to update it 🤔 The closest is here while again, don't think it is somehow exposed to task
t
would have to look closer to make sure that field is safe to use. could you help us understand what the end use case is here btw?
l
we are an infra team developing a decorator to be used on customer's task, which intend to 1. sanity check such as ensure input/output type 2. create a contract that can be used later on in operation pipeline for 2) we'd like to allocate that decorated task and get user output
t
what do you mean by get user output?
l
the task is expected to return certain type of object, and we are interested in reading that
Copy code
// workflow code
@task
@my_decorator
def user_function() -> Foo

// flyte remote
execution = remote.get....
node = execution.find_node_for_user_function()
// do something with node.outputs
so this 
find_node_for_user_function
does not seem to be doable 😓
t
wait why is the custom decorator below the task decorator?
l
i would need to output of the task, hence below. We are adjusting the design based on what flyte can provide. For now, it looks like node searching based on custom tag is not feasible so we are trying to confirm with the community if there's a path to do this 😄
t
I don’t think tags is used by admin/propeller, feel free to use it.
we’re trying to move away from model files, but haven’t had the time.
so if you want to use it’ll still need to be updated.
l
exactly
thanks for confirming
that gave me confusion when I see tags under metadata and did not see anything available on the client side 😄
t
oh sorry
yeah we really need to get rid of them. they’re a vestige of python 2 😞
l
thanks for the help. We'll change our design accordingly 😄
4 Views
Open in Slack
PreviousNext
Powered by