https://flyte.org logo
#ask-the-community
Title
# ask-the-community
t

Tom Touati

03/10/2024, 2:33 PM
Hey all, is there a way to view the source code of a registered workflow after it is registered?
k

Ketan (kumare3)

03/10/2024, 3:13 PM
Haha folks have asked about this, there is a way. Infact @Thomas Fan just merged something into Flyte devs also maybe @L godlike
I do feel we can add it to the description of a Task though
t

Tom Touati

03/10/2024, 3:15 PM
Great. Our dev ops guy didn't implement ci registration yet so it's a real life saver 😃
k

Ketan (kumare3)

03/10/2024, 3:16 PM
Wdym
If you have ideas let’s put them together about usecases
t

Tom Touati

03/10/2024, 3:28 PM
I mean that the standard way to link between a task and it's code would be to register during ci, which will link the task version with the commit_hash. I assume that's what most users do.
k

Ketan (kumare3)

03/10/2024, 3:34 PM
Yes - that is somewhat supported already, if you add some docs link.
t

Tom Touati

03/10/2024, 3:52 PM
wdym?
t

Tom Touati

03/10/2024, 4:39 PM
K, thanks! Hope I'll get an answer soon about retrieving the task's source code
k

Kevin Su

03/11/2024, 3:57 AM
t

Tom Touati

03/11/2024, 9:19 AM
@Kevin Su Thx but i'm afraid this doesn't help. I'll explain my case - I have a task version that yielded 88% accuracy, which then changed and started to yield 50% in later versions. I don't have a reference to the source code of the 88% accuracy task. I can only treat this task version as a black box, which I hoped flyte can help me retrieve and deserialize/restore the code from.
Actually, I've just downloaded the tar.gz file with all the task's code, pretty straight forward. Thanks anyways guys!
k

Ketan (kumare3)

03/11/2024, 3:21 PM
Yes we should link to the fast registered tarball