google-app-engine

Can't shutdown app engine version. Keeps billing

梦想的初衷 提交于 2021-02-07 03:37:25
问题 I am not able to stop and consequently delete a app engine version. I have 3 different versions at the moment, under the same default service: gappa-v1 , which is currently serving 100% of the traffic mg-v1 , which is currently stopped 20170223t163224 I am able to stop, restart and delete all the versions but the 20170223t163224 version. I have tried everything, both from the Google Cloud Console, and the gcloud command-line tool. Interacting from the Google Cloud Console is kinda useless

Enforce Cache-Control in Google Cloud Endpoints

混江龙づ霸主 提交于 2021-02-07 01:57:39
问题 My endpoint method generates a different response for each invocation regardless of the parameter list. I often see my client call the endpoint with the same parameter list, and the front end instance returns a cached response. In the official documentation I read that ApiMethod#cacheControl has been deprecated. On the other hand, the documentation says that the @Api-scopped annotation @ApiCacheControl has not been implemented yet so adding the following makes no difference. cacheControl =

Enforce Cache-Control in Google Cloud Endpoints

浪子不回头ぞ 提交于 2021-02-07 01:56:03
问题 My endpoint method generates a different response for each invocation regardless of the parameter list. I often see my client call the endpoint with the same parameter list, and the front end instance returns a cached response. In the official documentation I read that ApiMethod#cacheControl has been deprecated. On the other hand, the documentation says that the @Api-scopped annotation @ApiCacheControl has not been implemented yet so adding the following makes no difference. cacheControl =

Enforce Cache-Control in Google Cloud Endpoints

我的未来我决定 提交于 2021-02-07 01:55:17
问题 My endpoint method generates a different response for each invocation regardless of the parameter list. I often see my client call the endpoint with the same parameter list, and the front end instance returns a cached response. In the official documentation I read that ApiMethod#cacheControl has been deprecated. On the other hand, the documentation says that the @Api-scopped annotation @ApiCacheControl has not been implemented yet so adding the following makes no difference. cacheControl =

Enforce Cache-Control in Google Cloud Endpoints

柔情痞子 提交于 2021-02-07 01:54:38
问题 My endpoint method generates a different response for each invocation regardless of the parameter list. I often see my client call the endpoint with the same parameter list, and the front end instance returns a cached response. In the official documentation I read that ApiMethod#cacheControl has been deprecated. On the other hand, the documentation says that the @Api-scopped annotation @ApiCacheControl has not been implemented yet so adding the following makes no difference. cacheControl =

Enforce Cache-Control in Google Cloud Endpoints

可紊 提交于 2021-02-07 01:54:20
问题 My endpoint method generates a different response for each invocation regardless of the parameter list. I often see my client call the endpoint with the same parameter list, and the front end instance returns a cached response. In the official documentation I read that ApiMethod#cacheControl has been deprecated. On the other hand, the documentation says that the @Api-scopped annotation @ApiCacheControl has not been implemented yet so adding the following makes no difference. cacheControl =

How can I grant the account permission to list enabled APIs?

纵饮孤独 提交于 2021-02-06 15:49:35
问题 During a build on Cloud Build, I get the following warning: Step #2: WARNING: Unable to verify that the Appengine Flexible API is enabled for project [xxxxx]. You may not have permission to list enabled services on this project. If it is not enabled, this may cause problems in running your deployment. Please ask the project owner to ensure that the Appengine Flexible API has been enabled and that this account has permission to list enabled APIs. I'd like to get rid of this warning to get a

What is the maximum memory a Google App Engine app may consume?

梦想的初衷 提交于 2021-02-06 15:27:05
问题 What is the maximum amount of local memory ( not Memcache) each instance of a Google App engine app is allowed to consume? I couldn't find any information on the GAE quotas page. 回答1: The maximum memory limit for an App Engine instance depends on the instance class that you choose. The default limit is 128 MB. The following classes are currently available: F1 and B1 - 128 MB F2 and B2 - 256 MB F4 and B4 - 512 MB F4_1G and B4_1G - 1024 MB Edit: Second generation instances have double the

What is the maximum memory a Google App Engine app may consume?

时光总嘲笑我的痴心妄想 提交于 2021-02-06 15:23:02
问题 What is the maximum amount of local memory ( not Memcache) each instance of a Google App engine app is allowed to consume? I couldn't find any information on the GAE quotas page. 回答1: The maximum memory limit for an App Engine instance depends on the instance class that you choose. The default limit is 128 MB. The following classes are currently available: F1 and B1 - 128 MB F2 and B2 - 256 MB F4 and B4 - 512 MB F4_1G and B4_1G - 1024 MB Edit: Second generation instances have double the

How to log Stackdriver log messages correlated by trace id using stdout Go 1.11

邮差的信 提交于 2021-02-06 11:57:10
问题 I'm using Google App Engine Standard Environment with the Go 1.11 runtime. The documentation for Go 1.11 says "Write your application logs using stdout for output and stderr for errors". The migration from Go 1.9 guide also suggests not calling the Google Cloud Logging library directly but instead logging via stdout. https://cloud.google.com/appengine/docs/standard/go111/writing-application-logs With this in mind, I've written a small HTTP Service (code below) to experiment logging to