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

Flyte

Hi there, we've been having some challenges with the token cache for flytectl inside devcontainers. The use of gnome keyring inside docker containers is <https://alex-ber.medium.com/using-gnome-keyring-in-docker-container-2c8a56a894f7|tricky business>. Is there a possibility of moving to a more straightforward (file based say) token cache instead?

If we look at how awscli does it, they store token in `~/.aws/sso/cache` which is really nice because you can login once on your host machine and map this volume into devcontainers. I think a similar model should be possible for flytectl.

in flytekit, contributing is really straightforward

also in flytekit you can simply use the keyrings.alt package which does this (insecure) really