It was more a question because the documentation was unclear for 2nd generation standard GAE environments. I have no problem using an explicit credentials file - in fact I prefer that to the magic of default credentials, and using the GCE metadata service involves an extra network hop if I'm not mistaken.
On Tuesday, September 25, 2018 at 4:50:57 PM UTC-4, Stewart Reichling wrote: > > Hi Eric -- can you follow up with more details about your use case? > > On Tuesday, September 18, 2018 at 10:02:24 AM UTC-7, Eric G wrote: >> >> Thanks! I think I will stick with using an explicit service account json >> file, but it's good to know this route works. >> >> On Monday, September 17, 2018 at 3:43:43 PM UTC-4, David (Google Cloud >> Support) wrote: >>> >>> Python 3.7 on App Engine standard provides the GCE metadata service, so >>> as an alternative, you could use Compute Engine Credentials >>> <https://cloud.google.com/docs/authentication/production#auth-cloud-compute-engine-python>. >>> >>> I will inform our documentation team to update this document since it is >>> outdated and it does not include App Engine Standard Second Generation as >>> one of the platforms where you could use these credentials. >>> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/e46520e4-b680-422b-baec-6b983145043b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
