The issue you're encountering, where environment variables passed to Flyte in uppercase are rendered as lowercase, appears to be a recognized bug within the Flyte ecosystem. This behavior has been noted and discussed in the Flyte community, particularly in the context of the Flyte MLFlow plugin and other components. The discussions suggest that this is not an isolated incident but rather a broader issue that affects various parts of the Flyte system.
From the context provided, it's clear that this issue has been acknowledged by key members of the Flyte community, including Kevin Su, who confirmed it as a bug and prioritized its resolution. The problem persists across different versions of Flyte, including 1.4.0 and 1.4.2, indicating that it was not resolved in those updates. The discussions also highlight that this issue is not specific to any single plugin or configuration but affects environment variables more generally within the Flyte ecosystem.
The underlying cause of this issue has not been explicitly detailed in the provided discussions. However, the acknowledgment by Flyte developers and their commitment to addressing it suggests that it is recognized as a problem with the system itself, rather than user error or misconfiguration.
Given the nature of this issue, the best course of action would be to follow the discussions on the Flyte community forums and GitHub for updates on the bug's resolution. Additionally, engaging with the community by providing any further details of your own experience with this issue could help the developers understand its scope and impact, potentially accelerating a fix.
---
This is an AI-generated response, take its recommendations with caution.
Please help us improve the model accuracy by giving this response a thumbs up/thumbs down reaction.
Sources
https://discuss.flyte.org/t/10042573/i-ve-just-realised-all-the-environment-variable-defined-with/
https://github.com/flyteorg/flyte/issues/4503/ 👍 button 👎 button