Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
None
-
None
Description
The only problem with google cloud, are credentials.
We cannot match google credentials with AWS Key|Secret, they have much more
example of config file
cat ~/.xbench/mariadb-clustrix-xbench.json
|
{
|
"type": "service_account",
|
"project_id": "mariadb-clustrix",
|
"private_key_id": "XXXXXXX",
|
"private_key": "-----BEGIN PRIVATE KEY-----\nXXXX-----END PRIVATE KEY-----\n",
|
"client_email": "xbench@mariadb-clustrix.iam.gserviceaccount.com",
|
"client_id": "111124267925349327701",
|
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
|
"token_uri": "https://oauth2.googleapis.com/token",
|
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
|
"client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/xbench%40mariadb-clustrix.iam.gserviceaccount.com"
|
}
|
documentation
https://cloud.google.com/iam/docs/service-accounts
so we need just UX decision, is it convenient to make all this json fields session variables for google cloud, or we want to have one, containing full json config, or any other ideas
Attachments
Issue Links
- is part of
-
MCOL-5013 Support Load data from AWS S3 : UDF : columnstore_info.load_from_s3
-
- Closed
-