Memcache is a shared service <https://cloud.google.com/appengine/docs/python/memcache/> which uses memory, but this is independent of your instance's local memory. It will not get flushed, and neither will Datastore data, where OAuth tokens are typically persisted. In practice, users will not notice a traffic relocation (barring any application issues with the new version) much the same as they would not notice traffic being served from a different instance clone.
On Monday, September 26, 2016 at 1:52:57 PM UTC-4, Vladimir S wrote: > > Hi, > > > I have a simple python 2.7 webapp2 site in GAE which makes users > authenticate via Oauth 2.0 to grab their Google+ full name to display on a > hello world page. Would users of such site get errors or notice issues > during a traffic relocation (silent deployment) to a new version with > changed hello world message? The URL is kept the same but I still don't > know if the Oauth tokens will remain valid. Will memcache have any part of > this switch or is it reset after deployment? > > > Thanks > > > PS. I posted this on SO earlier but I think the question is more relevant > here. > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/1e90c61a-344d-4f37-8276-4cf564a005cb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
