<#7367 feat(tasklog): add runName and actionName t...
# flyte-github
a
#7367 feat(tasklog): add runName and actionName template vars Pull request opened by pingsutw TL;DR Restore the
runName
and
actionName
template variables that exist in v1's
tasklog
engine but were never ported to v2. User-supplied deeplink URLs that reference these placeholders (e.g. a wandb URL like
.../runs/{{.runName}}-{{.actionName}}
) currently pass through literally because v2 doesn't register them, leaving the link broken. Changes •
flyteplugins/go/tasks/pluginmachinery/tasklog/template.go
• Add
RunName
and
ActionName
to
templateRegexes
and register their regexes in
initDefaultRegexes
. • Populate them in
templateVars()
when
TaskExecutionID.NodeExecutionId.ExecutionId
is set.
RunName
mirrors
executionName
(
NodeExecutionId.ExecutionId.Name
) for v1 compatibility;
ActionName
is
NodeExecutionId.NodeId
. •
flyteplugins/go/tasks/pluginmachinery/tasklog/template_test.go
• Set
NodeId: "my-node-id"
in the fixture and assert the two new template vars in the existing
task execution happy path
case. This mirrors the v1 implementation in
flyteplugins/go/tasks/pluginmachinery/tasklog/template.go
(variables introduced upstream for the v1 path). Type • Bug Fix • Feature Are all requirements met? • Code completed • Smoke tested • Unit tests added flyteorg/flyte