[google-appengine] Re: Cloud Build - Multiple Environments

[Bilal Haidar]

This is what happens inside Cloud Build:

---
Services to deploy:

*descriptor: [/workspace/app.yaml]*
source: [/workspace]
target project: [test-project]
target service: [default]
target version: [qa]
target url: [https://test-project.uc.r.appspot.com]



On Wednesday, June 9, 2021 at 9:50:01 AM UTC+3 Bilal Haidar wrote:

>
> In my app, I have the following:
>
> - app.yaml
> - cloudbuild.yaml
> ---
> I use the above for the first time to deploy the default service.
>
> - app.qa.yaml
> - cloudbuild_qa.yaml 
>
> - app.staging.yaml
> - cloudbuild_staging.yaml 
>
> - app.prod.yaml
> - cloudbuild_prod.yaml 
>
> They all reside at the root of the app.
>
> For instance, the cloudbuild_qa.yaml is as follows:
>
> steps:
>   - name: node:14.0.0
> entrypoint: npm
> args: ['install']
>   - name: node:14.0.0
> entrypoint: npm
> args: ['run', 'prod']
>   - name: 'gcr.io/cloud-builders/gcloud'
> args: ['beta', 'app', 'deploy', '--project', '$PROJECT_ID', '-q', 
> '$_GAE_PROMOTE', '--version', '$_GAE_VERSION', '--appyaml', 'app.qa.yaml']
> timeout: '3600s'
>
> The Cloud Build works well, however, it's not respecting the `app.qa.yaml` 
> instead, it always takes the default `app.yaml`.
>
> Any idea what's happening? Do you know how to use the correct app.yaml 
> file in such a case?
>

-- 
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/9c483255-9745-489b-b3cd-d5d620a8007fn%40googlegroups.com.

[google-appengine] Cloud Build - Multiple Environments

[Bilal Haidar]

In my app, I have the following:

- app.yaml
- cloudbuild.yaml
---
I use the above for the first time to deploy the default service.

- app.qa.yaml
- cloudbuild_qa.yaml 

- app.staging.yaml
- cloudbuild_staging.yaml 

- app.prod.yaml
- cloudbuild_prod.yaml 

They all reside at the root of the app.

For instance, the cloudbuild_qa.yaml is as follows:

steps:
  - name: node:14.0.0
entrypoint: npm
args: ['install']
  - name: node:14.0.0
entrypoint: npm
args: ['run', 'prod']
  - name: 'gcr.io/cloud-builders/gcloud'
args: ['beta', 'app', 'deploy', '--project', '$PROJECT_ID', '-q', 
'$_GAE_PROMOTE', '--version', '$_GAE_VERSION', '--appyaml', 'app.qa.yaml']
timeout: '3600s'

The Cloud Build works well, however, it's not respecting the `app.qa.yaml` 
instead, it always takes the default `app.yaml`.

Any idea what's happening? Do you know how to use the correct app.yaml file 
in such a case?

-- 
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/d81efeac-564f-484c-ad58-ea28643b19fen%40googlegroups.com.

[google-appengine] Multiple environments with Cloud Build

[Bilal Haidar]

Hello,
I have a Laravel PHP app. I need to deploy it into several "versions".

Accordingly, I added a new folder `/ci`

Inside this folder I have files like:

`qa.app.yaml`
`qa.cloud_build.yaml`

However, when this CloudBuild runs, it's taking the `/app.yaml` file 
instead.

Later, I need to add files for staging and production.

How should I structure those files so that CloudBuild uses the correct 
app.yaml file?

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/60bb2e52-2367-434c-92d3-12994c0aa552n%40googlegroups.com.

Re: [google-appengine] Re: Larger MongoDB Query from App Engine neither succeeding nor failing nor throwing exception

[Bradley Barrows]

This is exactly the article I have been looking for. Thank you so much!

I will respond if I can find any specific information related to this issue
in case anyone else runs into a similar problem in the future as well.

Thank you so much,
Brad

On Tue, Jun 8, 2021 at 4:45 AM 'Angel (Google Cloud Platform Support)' via
Google App Engine  wrote:

> Hello Brad,
>
> to my knowledge there are no direct data limits in App Engine when used
> over TCP. There are, however, some architectural considerations that are
> worth being aware of for Google Cloud Platform. You can find the related
> article in [1]. It details some use cases in which a final user might
> experience latency issues or network inefficiencies. I believe it might
> give you some insight as to what might be happening in your case.
>
> Kind regards.
> __
> [1] -
> https://cloud.google.com/architecture/tcp-optimization-for-network-performance-in-gcp-and-hybrid
>
> On Tuesday, June 8, 2021 at 9:05:34 AM UTC+2 bradeba...@gmail.com wrote:
>
>> Hi
>>
>> This weekend we ran into an issue. A function, using Mongoose (a NodeJS
>> MongoDB library) was making a pretty simple query, which when run locally
>> either by running the query directly or when running the entire Node server
>> directly ran fine.
>>
>> However, when deployed to Google App Engine we noticed that logging was
>> logged out up until we awaited the query to MongoDB and then never
>> continued. No exception was ever logged as well.
>>
>> It is as if the Mongo query was taking too long and App Engine just
>> killed the Node process all together.
>>
>> The server did return a 500 error. I believe it was a 503 specifically.
>>
>> We ended up realizing by using limit or projection we could decrease the
>> response size of the query and get a result and the execution of the NodeJS
>> application would continue.
>>
>> Now if Mongo was an HTTP server I would see that there is a 32MB maximum
>> request size and be able to find that there are only so many records I can
>> query at once. However, since this is a TCP connection to the Mongo server
>> I cannot find any quotas or limitations on how much data a TCP connection
>> from an App Engine server can send or receive.
>>
>> As we know that decreasing the size of the response from MongoDB fixed
>> our issue, I believe it is safe to say the issue is related to the amount
>> of data sent/received or more specifically received over TCP when
>> communicating with an App Engine server.
>>
>> Does anyone have any details on known limitations of App Engine
>> communicating with other services over TCP?
>>
>> Thank you so much!
>> Brad
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/Lj6qaT2lC90/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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/6d0562a1-a9e7-4baf-ba03-0335ffa9568dn%40googlegroups.com
> 
> .
>

-- 
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/CAGJGpkoNKVS2Oyyh%2B6PEiaCaY63O27WtFX21jATFmZqPYpcYjA%40mail.gmail.com.

[google-appengine] Re: Larger MongoDB Query from App Engine neither succeeding nor failing nor throwing exception

['Angel (Google Cloud Platform Support)' via Google App Engine]

Hello Brad,

to my knowledge there are no direct data limits in App Engine when used 
over TCP. There are, however, some architectural considerations that are 
worth being aware of for Google Cloud Platform. You can find the related 
article in [1]. It details some use cases in which a final user might 
experience latency issues or network inefficiencies. I believe it might 
give you some insight as to what might be happening in your case.

Kind regards.
__
[1] 
- 
https://cloud.google.com/architecture/tcp-optimization-for-network-performance-in-gcp-and-hybrid

On Tuesday, June 8, 2021 at 9:05:34 AM UTC+2 bradeba...@gmail.com wrote:

> Hi
>
> This weekend we ran into an issue. A function, using Mongoose (a NodeJS 
> MongoDB library) was making a pretty simple query, which when run locally 
> either by running the query directly or when running the entire Node server 
> directly ran fine.
>
> However, when deployed to Google App Engine we noticed that logging was 
> logged out up until we awaited the query to MongoDB and then never 
> continued. No exception was ever logged as well.
>
> It is as if the Mongo query was taking too long and App Engine just killed 
> the Node process all together.
>
> The server did return a 500 error. I believe it was a 503 specifically.
>
> We ended up realizing by using limit or projection we could decrease the 
> response size of the query and get a result and the execution of the NodeJS 
> application would continue.
>
> Now if Mongo was an HTTP server I would see that there is a 32MB maximum 
> request size and be able to find that there are only so many records I can 
> query at once. However, since this is a TCP connection to the Mongo server 
> I cannot find any quotas or limitations on how much data a TCP connection 
> from an App Engine server can send or receive.
>
> As we know that decreasing the size of the response from MongoDB fixed our 
> issue, I believe it is safe to say the issue is related to the amount of 
> data sent/received or more specifically received over TCP when 
> communicating with an App Engine server.
>
> Does anyone have any details on known limitations of App Engine 
> communicating with other services over TCP?
>
> Thank you so much!
> Brad

-- 
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/6d0562a1-a9e7-4baf-ba03-0335ffa9568dn%40googlegroups.com.

[google-appengine] Re: Can I configure GAE Standard to support TLS 1.2 and laters?

['Hamid Raza' via Google App Engine]

Hi Tam,

There are two possibilities to do so.

1. Contact the Google support team and ask them to configure TLS 1.2 for 
you. To do so you will have to buy a support plan first.
2. Configure the load balancers by yourself to support TLS 1.2. You will 
have to loom into the load balancers docs in detail for that.

Thanks!

On Tuesday, June 8, 2021 at 12:05:14 PM UTC+5 tam...@gmail.com wrote:

> Hi folks,
>
> It seems GAE doesn't support TLS 1.2 and later versions, Any setting I can 
> change?
>
> Thanks,
> Tam
>

-- 
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/f8fc7bdc-a1aa-4d9a-bffa-b7ec77fec98an%40googlegroups.com.

[google-appengine] Larger MongoDB Query from App Engine neither succeeding nor failing nor throwing exception

[Bradley Barrows]

Hi

This weekend we ran into an issue. A function, using Mongoose (a NodeJS 
MongoDB library) was making a pretty simple query, which when run locally 
either by running the query directly or when running the entire Node server 
directly ran fine.

However, when deployed to Google App Engine we noticed that logging was 
logged out up until we awaited the query to MongoDB and then never 
continued. No exception was ever logged as well.

It is as if the Mongo query was taking too long and App Engine just killed 
the Node process all together.

The server did return a 500 error. I believe it was a 503 specifically.

We ended up realizing by using limit or projection we could decrease the 
response size of the query and get a result and the execution of the NodeJS 
application would continue.

Now if Mongo was an HTTP server I would see that there is a 32MB maximum 
request size and be able to find that there are only so many records I can 
query at once. However, since this is a TCP connection to the Mongo server 
I cannot find any quotas or limitations on how much data a TCP connection 
from an App Engine server can send or receive.

As we know that decreasing the size of the response from MongoDB fixed our 
issue, I believe it is safe to say the issue is related to the amount of 
data sent/received or more specifically received over TCP when 
communicating with an App Engine server.

Does anyone have any details on known limitations of App Engine 
communicating with other services over TCP?

Thank you so much!
Brad

-- 
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/4085b9f4-a849-459f-aab6-43f2b636d253n%40googlegroups.com.

[google-appengine] Google App Engine TCP Connections

[Bradley Barrows]

Hi

I have a NodeJS App Engine server which is awaiting a MongoDB query which, 
when reaching a certain size, never returns. There is no exception thrown 
from App Engine either. It is as if the process is just killed because 
execution flow and therefore logging from the process making the MongoDB 
query stops.

If this were a request to a HTTP server I could look at the limits and 
quotas page and see that a maximum of 32MB requests and response size is 
allowed.

I am unable to find any limits or quotas for TCP connections from an App 
Engine server.

We temporarily solved the issue by using a limit or projection to decrease 
the amount of data returned by the MongoDB query. When less data is sent 
back to the App Engine server execution continues and the server runs as 
expected.

I was wondering if it was possible if at some point if TCP data usage 
reaches a limit will the App Engine process be killed? Without any logging? 
Why would the execution of the process handling the response that fires off 
the MongoDB query stop and no exception or anything further be logged?

Thank you
Brad

-- 
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/2ace1818-2ac8-49d4-bcec-0980c30eeb78n%40googlegroups.com.

[google-appengine] Can I configure GAE Standard to support TLS 1.2 and laters?

[Tam Nagasada]

Hi folks,

It seems GAE doesn't support TLS 1.2 and later versions, Any setting I can 
change?

Thanks,
Tam

-- 
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/edf60f81-170e-473b-9bc5-f01e01799a36n%40googlegroups.com.