Greg Linklater
02/12/2024, 11:39 AMGlime
02/12/2024, 11:40 AMflytekit.current_context().execution_id.name
as mentioned by Evan Sadler and Ketan (kumare3) (source). 5. Runtime Timestamps: Information about when a node or task was created, started, and updated is available. This includes created_at
, started_at
, and updated_at
timestamps (source). 6. Execution Parameters: Execution parameters contain most of the information needed, and it's recommended to use execution parameters instead of environment variables for future optimizations (source). This data can be used for various purposes, including resource management, associating resources with metadata, and understanding the execution flow and performance of tasks within workflows.Greg Linklater
02/12/2024, 11:53 AMGlime
02/12/2024, 11:53 AMGreg Linklater
02/12/2024, 12:55 PMGlime
02/12/2024, 12:56 PMimport os # Assuming 'FLYTE_PROJECT' is the name of the environment variable that holds the project name project_name = os.getenv('FLYTE_PROJECT') print(f"The project name is: {project_name}")
Please replace 'FLYTE_PROJECT'
with the actual name of the environment variable that Flyte sets for the project name. If you're unsure about the exact name of this environment variable, you may need to consult the Flyte documentation or reach out to the Flyte community for more specific guidance. For more detailed information on configuring your Flyte deployment and understanding how environment variables can be used within Flyte tasks, you might find the Flyte documentation helpful. Specifically, the "Configuring Your Flyte Deployment" section might provide more insights (Configuring Your Flyte Deployment).Ketan (kumare3)
Greg Linklater
02/13/2024, 12:40 PMexecution_id
and task_id
) but one thing I am still missing is being able to access the name
and version
of the workflow that is executing the task.Greg Linklater
02/13/2024, 12:40 PM