👋 Quick question about reference launch plans: • I noticed that when launching them, Flyte Propeller actually hits Admin's

CreateExecution

endpoint • But we actually intercept this request in a proxy service to inject user identity info, and we can't identify the user accurately when the call comes from a service like Propeller • However, the request from Propeller already has the identity fields filled out correctly - I was wondering if it copies the

ExecutionCreateRequest

of the original execution, particularly fields like labels, security context, tags to launch the reference LP? ◦ Any code pointers to where this is done would be very helpful! I think it ends up here where it copies the request from the launch context but I wasn't able to trace this back to the place where it calls this for a reference launch plan

@gentle-night-59824 yes, when a reference launchplan is executed, flytepropeller makes a call to the

CreateExecution

endpoint. The

ExecutionCreateRequest

is constructed using information from the Launch Context which includes fields like security contexts, labels and annotations.