Hey team!

Currently, @secrets supports only AWS Secrets Manager. Contact us on Metaflow support Slack if you are interested in using another secrets manager.

Are there any plans to support the @secrets decorator for GCP users? It seems ideal for flows that you wish to run remotely and locally. Currently as a workaround, I’m using the @kubernetes decorator to access secrets I sync to the cluster from GSM. I couldn’t seem to override that with

enviornment=local

so I ended up putting a fork in my DAG (based on a separate parameter) to support both the remote (using the @kubernetes decorator) and local versions of this step. Given that this flow is running at scale with Argo Workflows (which has been awesome), this fork is not ideal because it results in a few extra steps consuming resources. It also requires individuals to be authenticated with Kubernetes in order to run this flow locally. I experimented with conditional decorator application using

functools

but this seemed to cause compilation issues. Thanks!