<#7214 [V2] Set ReportUri in ActionEvent output re...
# flyte-github
a
#7214 [V2] Set ReportUri in ActionEvent output references Pull request opened by pingsutw Tracking issue Why are the changes needed? The
OutputReferences
proto (
flyteidl2/task/common.proto
) defines both
output_uri
and
report_uri
, but the executor only populated
output_uri
when building `ActionEvent`s. Consumers that need the HTML report URI had no way to locate it. What changes were proposed in this pull request? In
executor/pkg/controller/taskaction_controller.go
,
outputRefs
now also sets
ReportUri
using the convention path
<outputPrefix>/report.html
, alongside the existing
<outputPrefix>/outputs.pb
. How was this patch tested? image Added a unit test in
executor/pkg/controller/output_refs_test.go
that verifies: • The report URI ends with
/report.html
. • The report URI and output URI share the same directory prefix.
Copy code
go test ./executor/pkg/controller/ -run TestOutputRefs -count=1
ok  	<http://github.com/flyteorg/flyte/v2/executor/pkg/controller|github.com/flyteorg/flyte/v2/executor/pkg/controller>	0.851s
Labels • changed Setup process Screenshots Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. Related PRs Stack •
main
• #6583 • [V2] Set ReportUri in ActionEvent output references 👈 Docs link flyteorg/flyte