Might be better to ask about this here - thanks! ...
# contribute
e
Might be better to ask about this here - thanks! The issue is around how version strings are calculated (and this seems to be a bug for agents b/c it's not taking all inputs into consideration)
k
how do you register the workflow? pyflyte run?
if you use
pyflyte run or register
, the version should be different when you change the code or task config.
e
We found that changing the task config does not actually change the version of the workflow (and Ketan mentioned this is a controversial topic)
There's a little discussion at https://github.com/flyteorg/flyte/issues/5364
We're going to take a different tack on this one and move things that are currently variable and tracked in our task_config over to be proper inputs in Flyte -- which should solve our problem
r
Here is the workflow I have in mind, I believe an error happens on the second time it's run
Copy code
from flytekit import task, workflow


@task
def say_hello(name: str) -> str:
    return f"Hello, {name}!"


@workflow
def wf() -> str:
    import datetime
    name = str(datetime.datetime.now())
    res = say_hello(name=name)
    return res
edit: I think this workflow does not follow Flyte principles, the datetime logic should be extracted into its own task, and then resolved as a promise.