@Anna Geller forgot to ask whether there is a way at the moment to custom set the instance of the flow run instead of these auto generated names?
a
Anna Geller
04/23/2022, 7:25 PM
Are you saying you don't like intelligent cows, awesome chickens, and other cute animals? π
I heard that we may expose this functionality in the future, but I have no info about the timeline; afaik this is not considered a high priority item
But you can name your flows and deployments which can probably already help? depending on how you work with it and what's your preference
π€£ 1
Anna Geller
04/23/2022, 7:30 PM
currently, when you navigate in the UI, even though my flow run has the name
georgeous-snake
, I can see in the breadcrumb that it's a run of a flow named "dask-flow"
if you use sensible flow names and you attach additional tags to your
DeploymentSpec
, it shouldn't be too difficult to find the right info. But you can explain your use case more if I misunderstood what you are trying to do
s
Sander
04/23/2022, 7:35 PM
:) although I love gorgeous snakes, it would be nice to adjust that text to say a datetime of the run or something. Indeed specifying the flow with a specific name is good, this additional feature would be helpful in case this is used for 100s of flows each on their own schedules. I think tags are also not flowrun specific right?
a
Anna Geller
04/23/2022, 7:52 PM
You're right, tags are attached to deployments so they wouldn't change on a per run basis
I definitely agree that a more use-case-specific flow run names would be more helpful in troubleshooting than funny animal names, but I lost that battle π animals won. But custom run names are definitely on the roadmap, I'll keep your use case in mind if the topic should come up during product office hours
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.