New RunLLM response generated: >>>*# Question* Is there a way to get the principal that kicked off an execution in a flyte propeller plugin? I noticed that the presto plugin tries to pull the principal from the context but its not present. # Answer The principal information is typically captured in the execution metadata and can be accessed through Flyte Admin. However, it seems that Flyte Propeller does not directly expose the principal in the context for plugins. According to this GitHub issue, the principal is passed as "unknown" by default when launching new executions. Would you like more detail on how to potentially work around this limitation? Sources: - Core Feature: Flyteadmin should pass the current principal and nesting level to Flytepropller Slack Link https://.slack.com/archives/CP2HDHKE1/p1730240402.746159 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.