#7141 fix: propagate action group through TaskAction CRD to runs service Pull request opened by AdilFayyaz Why are the changes needed? The UI groups related actions under a collapsible folder using ActionMetadata.group, but actions were always recorded with an empty group because the field was silently dropped at the TaskAction CRD boundary. What changes were proposed in this pull request? • Added Group field to TaskActionSpec and wired it through SetActionSpec / GetActionSpec • Pass Group in RecordActionRequest when the actions service notifies the runs service of a new action • Fixed convertActionToEnrichedProto to always populate ActionMetadata (including Group) rather than conditionally on ParentActionName • Regenerated CRD manifests to allow k8s to accept the group field on TaskAction resources How was this patch tested? • Ran local UI against sandbox with make -C manager run and verified that action groups render as collapsible folder items with their group name visible in the run sidebar Setup process Screenshots image Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. Related PRs Docs link •

main

• #6583 • fix: propagate action group through TaskAction CRD to runs service 👈 flyteorg/flyte