GoogleCloudPlatform / wordpress-plugins

WordPress plugin for Google App Engine
GNU General Public License v2.0
199 stars 57 forks source link

Notice: Project ID not given and Warning: Authenticated using end user credentials from Google #60

Open rickbeacham opened 6 years ago

rickbeacham commented 6 years ago

After updating the GCS plugin i received these two messages from my local development env.

Notice: A keyfile was given, but it does not contain a project ID. This can indicate an old and obsolete keyfile, in which case you should create a new one. To suppress this message, set suppressKeyFileNotice to true in your client configuration. To learn more about generating new keys, see this URL: https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating_service_account_keys in appengine/flexible/wordpress/wordpress-project/vendor/google/cloud/Core/src/ClientTrait.php on line 206 I'm not sure what Keyfile is needed? I never needed keyfile for this project.

Warning: Your application has authenticated using end user credentials from Google Cloud SDK. We recommend that most server applications use service accounts instead. If your application continues to use end user credentials from Cloud SDK, you might receive a "quota exceeded" or "API not enabled" error. For more information about service accounts, see https://cloud.google.com/docs/authentication/. To disable this warning, set SUPPRESS_GCLOUD_CREDS_WARNING environment variable to "true". in appengine/flexible/wordpress/wordpress-project/wordpress/wp-content/plugins/gcs/vendor/google/auth/src/Credentials/UserRefreshCredentials.php on line 102

I've setup my project_id to the correct project. I'm not sure why i'm seeing these messages. How can i test on my local machine?

All buckets were created in the Project and should be accessible by Service Accounts so I'm not sure why i'm suddenly getting this error.

ran-dall commented 6 years ago

@rickbeacham Check out #61. It may contain some helpful stuff.

The only thing I'm thinking it could relate to where you put the key. I was having the same issue until I moved it into /etc.

Also, this is kinda a Duplicate of #44