Summary
The user is looking for alternative ways to access workflow information within a task, specifically to retrieve the currently running workflow without using the discouraged fetch_workflow() method. They can obtain the execution ID but want to know how to get the workflow from it without using the flytekit Remote client. The user notes that the GIT_HASH is unavailable due to a migration to CI for image building and is trying to use flytekit.current_context().execution_id to fetch execution details and obtain the launch plan version. They express concerns about allowing flyte nodes to access the flyte admin proxy and are uncertain about the implications of this. Additionally, the user questions the relationship between task version and launch plan version, acknowledging that while they are usually the same, there are exceptions. They mention that their current execution seems to be local and that they are running this in a notebook. The user also suggests putting in a ticket for this issue and inquires about the possibility of contributing to the solution.