New RunLLM response generated: >>>*# Question* Hi all, has anyone tried relaunching a user's execution as a different user? I'm noticing that it's relaunched with the original identity rather than the current identity (which may have negative security implications). Wondering if others have noticed this. Thanks! # Answer Relaunching an execution in Flyte retains the original execution's metadata, including the identity of the user who initiated it. This behavior is by design, as per the ExecutionRelaunchRequest documentation. The

principal

field in

ExecutionMetadata

is overridden by Flyte Admin to ensure consistency and security, which means the original identity is preserved during relaunch. If you need to relaunch an execution with a different identity, you might need to manually adjust the identity context before initiating the relaunch. This can be complex due to Flyte's security model, which aims to maintain the integrity of execution metadata. Would you like more details on how to potentially work around this or further information on Flyte's security model? Sources: - ExecutionRelaunchRequest documentation - Flyte Admin identity context discussion Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1722880533.376099 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.