Skip to content

Commit

Permalink
add a commment
Browse files Browse the repository at this point in the history
Signed-off-by: Yee Hing Tong <[email protected]>
  • Loading branch information
wild-endeavor committed Jun 24, 2024
1 parent 9e47cc5 commit 66f6bfd
Show file tree
Hide file tree
Showing 6 changed files with 12 additions and 4 deletions.
4 changes: 2 additions & 2 deletions flyteidl/clients/go/assets/admin.swagger.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 2 additions & 0 deletions flyteidl/gen/pb-es/flyteidl/event/event_pb.ts

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 2 additions & 0 deletions flyteidl/gen/pb-go/flyteidl/event/event.pb.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 2 additions & 0 deletions flyteidl/gen/pb_rust/flyteidl.event.rs

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 2 additions & 0 deletions flyteidl/protos/flyteidl/event/event.proto
Original file line number Diff line number Diff line change
Expand Up @@ -115,12 +115,14 @@ message NodeExecutionEvent {
// Indicates if this node is an ArrayNode.
bool is_array = 22;

// Holding this field here for now, this will be upstreamed soon.
// So that Admin doesn't have to rebuild the node execution graph to find the target entity, propeller will fill this
// in optionally - currently this is only filled in for subworkflows. This is the ID of the subworkflow corresponding
// to this node execution. It is difficult to find because Admin only sees one node at a time. A subworkflow could be
// nested multiple layers deep, and you'd need to access the correct workflow template to know the target subworkflow.
core.Identifier target_entity = 23;

// Holding this field here for now, this will be upstreamed soon.
// Tasks and subworkflows (but not launch plans) that are run within a dynamic task are effectively independent of
// the tasks that are registered in Admin's db. Confusingly, they are often identical, but sometimes they are not
// even registered at all. Similar to the target_entity field, at the time Admin receives this event, it has no idea
Expand Down

0 comments on commit 66f6bfd

Please sign in to comment.