Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

<https://github.com/flyteorg/flyte/issues/6302> I tried the new `env_var` option with secrets, but when I run  a workflow locally it reverts to the old behaviour where it constructs the environment variable name using the group and key of the secret instead of checking for the `env_var` I set.

So I'm assuming there's no backend to update

And yes, the remote/my cluster is running `flyte-binary` v1.15.0