F

Flyte

Flyte enables you to build & deploy data & ML pipelines, hassle-free. The infinitely scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks. Explore and Join the Flyte Community!

Macro Replacement Issue in Dynamic Workflows

Summary

The user is facing issues with the {{ registration.version }} macro not being replaced correctly in dynamic workflows, suspecting that the runtime nature of these workflows is the cause, unlike classic workflows that evaluate the macro at registration time. They recognize that dynamic workflows do not currently support the macro and are considering hardcoding a version as a temporary solution. The user expresses a need for macro support due to their increased use of conditionals and dynamic workflows. They also mention their upcoming honeymoon, which may delay their ability to contribute to a solution. They plan to create an issue to describe their situation for future tracking.

Status
open
Tags
    Source
    #ask-the-community
      j

      joe.kelly

      9/30/2024

      thanks

      j

      joe.kelly

      9/30/2024

      Will do, I'll describe our situation in the issue

      k

      kumare

      9/30/2024

      create an issue for us to track later

      k

      kumare

      9/30/2024

      ohh ya, enjoy your honey

      j

      joe.kelly

      9/30/2024

      I think in general we're happy to contribute things back to the project when we can though!

      j

      joe.kelly

      9/30/2024

      I am about to head out on my honeymoon next week, so I am not the best one to get this done anytime soon :stuck_out_tongue_closed_eyes:

      k

      kumare

      9/30/2024

      the macro expansion, is in the translator

      k

      kumare

      9/30/2024

      should be straightforward

      k

      kumare

      9/30/2024

      would you be open to contributing

      k

      kumare

      9/30/2024

      hmm i would love an example

      j

      joe.kelly

      9/30/2024

      It would be great to have that macro supported -- as we're starting to integrate some agents into our processes, we're using conditionals more frequently (which is necessitating the use of more dynamic workflows)

      j

      joe.kelly

      9/30/2024

      Got it. Would the only real solution for now be to just hardcode a specific version of the workflow we want to call from our dynamic?

      k

      kumare

      9/30/2024

      dynamic wont work with the macro today, but it is possible to change that

      j

      joe.kelly

      9/30/2024

      Hi all -- has anyone used dynamic workflows in combination with reference launchplans (and specifically, the {{ registration.version }} macro)?

      We're observing an issue where it doesn't seem like the macro is getting properly replaced, and I'm wondering if the runtime nature of the dynamic workflow is the underlying cause (i.e., a "classic" workflow gets evaluated at registration time and thus the macro gets replaced properly, but because dynamic workflows skip that step, the macro never gets evaluated)?