[google-appengine] Error: Cannot sign data without `client_email`.
I am running GAE Flexible environment that is set up to use the default service account which has the Editor Role. Since last week I have started facing the below issue when connecting to GCS from GAE which results in the failure of the running process. *Error: Cannot sign data without `client_email`.* How do I fix this? What permissions do I need to provide to my GAE service account? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/caf4c988-eab0-4f0a-8d6b-f5f2657af943n%40googlegroups.com.
[google-appengine] Outbound Static IP for App Engine Flex Environment
Hi, I want to know how we can attach a static IP to the App engine instance using a flexible environment. According to the documentation this could be achieved for the standard environment using vpc_access_connector, but have not found anything for the flexible environment. Regards, -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/3292d607-b7d4-4ca0-a80b-bf5265f6cb6cn%40googlegroups.com.
[google-appengine] Re: App Engine Flexible Environment Deployed Version Management
Hi David, Thanks for this suggestion, As I mentioned we are using App Engine Flex Environment, even using the command: "gcloud app services set-traffic --splits =1" does not send traffic to the newer version which after running this command is supposed to be serving 100 % traffic. All the requests are still getting served by the previously deployed version of the app engine. What could be the possible issue in this case? On Friday, January 21, 2022 at 12:32:46 AM UTC+5 David (Cloud Platform Support) wrote: > You can deploy it this way: > > 1-gcloud app deploy --no-promote -v > > 2-gcloud app services set-traffic --splits =1 > > By using the no promote flag, when you perform a deployment, the new > version won’t directly serve traffic. Then, you could choose how much of > the traffic you want to be sent by using set traffic. > > If let’s say you want to send 50% of your traffic, you could do this: > > gcloud app services set-traffic --splits =.5,=.5 > > You could gradually send all traffic to the new version if that works > better for your use case. > > You could also do this within the UI. > On Thursday, January 20, 2022 at 7:58:21 AM UTC-5 Maha Farhat wrote: > >> Hi, >> We use App engine Flexible environment for executing long running >> asynchronous tasks. >> When we make changes to the app and deploy a new version using the >> command: "gcloud app deploy app.yaml", it deploys the new version routes >> 100% traffic to the newly deployed version, and stops the old version. This >> results in the failure of any request that was in process on the old >> version. >> >> We have tried keeping the old version alive by using the flag >> --no-stop-previous-version >> but in this case, even after the new version is deployed and the latest >> version is serving 100% requests the new request keeps getting served by >> the older version. 1. Is there a way to keep the old version running until >> the requests it is processing are completed? 2. How to make sure in the 2nd >> scenario that all the new requests after new deployment are served by the >> latest version instead of the old one? >> >> Thanks, >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2e7f7da4-b3a0-425f-ba94-cee58b2e3a4bn%40googlegroups.com.
[google-appengine] App Engine Flexible Environment Deployed Version Management
Hi, We use App engine Flexible environment for executing long running asynchronous tasks. When we make changes to the app and deploy a new version using the command: "gcloud app deploy app.yaml", it deploys the new version routes 100% traffic to the newly deployed version, and stops the old version. This results in the failure of any request that was in process on the old version. We have tried keeping the old version alive by using the flag --no-stop-previous-version but in this case, even after the new version is deployed and the latest version is serving 100% requests the new request keeps getting served by the older version. 1. Is there a way to keep the old version running until the requests it is processing are completed? 2. How to make sure in the 2nd scenario that all the new requests after new deployment are served by the latest version instead of the old one? Thanks, -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/f21fbaca-6a83-40d3-8ce0-1bd1d0f1151en%40googlegroups.com.
