hello 🙂 I am working from within a VSCode deployment and trying to get my metaflow flow into argo with minIO storage. I have a functional set-up of minIO and argo, but my set-up in the vscode deployment always returns the error message

Error: Unable to locate credentials

These credentials are in the

.metaflowconfig/config.json

and in the configmap of the VSCode deployment. I have checked which secrets are being used from within VSCode and the

METAFLOW_KUBERNETES_SECRETS

is set to the right secret. Do you have any idea what could lead to this

unable to locate credentials

or tests to figure it out? Should I test if my vscode deployment can make the flow appear on the Metaflow UI ? Thanks a bunch ⭐

@better-cat-13994 any more details on where exactly are you seeing

Error: Unable to locate credentials

? Can you paste the full stacktrace?

Here is a screenshot of the output and where I get the

Error: Unable to locate credentials

(inside VSCode running on kubernetes, in the same namespace as minIO and argo server) You also have my env variables set in the configmap of the VSCode service, which you can see on the VSCode Terminal are set (see

echo $METAFLOW_KUBERNETES_SECRETS

on last line) Does it give you more indication?

This looks like aws access issue. Can you first try exporting all aws access envs in this terminal where you are running? If that works, then you need to ensure your

~/.aws/credentials

has valid values

export AWS_ACCESS_KEY_ID=<your_own_ranom_stuff>
export AWS_SECRET_ACCESS_KEY=<more_random_stuff>
export AWS_SESSION_TOKEN=<again_random_stuff>

That would be strange because I am not using AWS in this project

But it does seem like you have set your data

"METAFLOW_DEFAULT_DATASTORE": "s3"

in the

~/.metaflow/config.json

I am doing a set-up similar to here (but with Argo instead of Airflow): https://github.com/outerbounds/metaflow-with-airflow-minio With minIO, I had understood that the

METAFLOW_DEFAULT_DATASTORE

had to be set to

s3

But you do have a point, I just reread and saw that step 8 sets AWS credentials. I'll have a closer look again 🙂