Thanks ShortElephant92 ! PR looks good, I'll ask the guts to take a look
Hi AgitatedDove14 I found the possible bug, I'll open a PR for it and we can discuss! It has to do with how we pass credentials to the GCS client.
For context, the google cloud storage SDK allows an authorized user credentials. This makes it a bit awkward for our developers already using their creds.
The error in question:2022-12-01 17:33:03,687 - clearml.storage - ERROR - Failed creating storage object gs://<my_bucket> Reason: Service account info was not in the expected format, missing fields token_uri, client_email.
I opened a PR for it, it has a bug attached to it too: https://github.com/allegroai/clearml/pull/841
Hi ShortElephant92
This isn't an issue if the user is using a Service Account JSON Key,
Are you saying that when you are using GS python sdk directly it works?
For context, the google cloud storage SDK allows an authorized user credentials.
ClearML actually uses the google python SDK, the JSON is just a way to pass the credentials to the google SDK, I'm not sure it points to "service account"? where did that requirement came from ?
is it from here Service account info was not in the expected format, missing fields token_uri, client_email. ?
Could that be the same issue?
https://stackoverflow.com/questions/43004904/accessing-gae-log-files-using-google-cloud-logging-python