Re: [google-appengine] Practical difference from Cloud Run

[Nicolas Grilly]

On Wed, Apr 10, 2019 at 11:23 PM Gabriel Axel  wrote:

> I watched the videos and read the docs of the new Cloud Run service and
> also took a look at the comparison table between GAE and Cloud Run, and to
> my understanding Cloud Run covers everything GAE Standard and Flexible do
> without any of their limitations. Maybe the only thing GAE "has over" Cloud
> Run is not having to write Dockerfile (except for Flexible custom runtime).
> Did I miss anything? Once Cloud Run goes GA, what use cases would be
> preferable for GAE over it?
>

I'm wondering the same. Can you share the link to the comparison table
between Cloud Run and App Engine you mentioned?

-- 
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/CAG3yVS7VEzzwrrtN46d5m2E%2Bc%3Dvb0W5TLVOfqkzgSgyA2mG6dQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: AppEngine Flex - Correct Firewall Configuration For Inter-Service-Communication

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

Hi David,

Thanks for bringing this to our attention, I will gladly submit this 
documentation improvement to the rightful team.

Thanks again and have a great day! 


On Wednesday, April 10, 2019 at 6:37:14 AM UTC-4, dvd gsng wrote:
>
> Hi Nicolas, thanks for verifying our results. We think that the GAE 
> documentation should be updated to reflect these restrictions more 
> explicitly, are you in a position to forward this to the appropriate team 
> by any chance?
>
> Thanks
> David
>
>
> On Wednesday, April 3, 2019 at 7:38:12 PM UTC+2, Nicolas (Google Cloud 
> Platform Support) wrote:
>>
>> Hi,
>>
>> Thanks for the screenshots! I’ve reproduced this and was able to confirm 
>> that if you switch the App Engine Firewall rules to “Deny All” and then try 
>> to granularly allow some IP address the app will return 403s. 
>>
>> This is most likely due to the internal App Engine infrastructure so I 
>> would recommend IAP as your best current solution to communicate between 
>> GAE services.
>>
>>
>> On Wednesday, February 27, 2019 at 10:20:33 AM UTC-5, dvd gsng wrote:
>>>
>>> Hi George, thanks for replying. Unfortunately, we've tried that, but it 
>>> didn't work out as expected. We added those two IPs (and two more, see 
>>> initial post) to the GAE firewall as well as the regular VPC firewall. 
>>> Please have a look that the images for reference:
>>>
>>> GAE firewall:
>>>
>>> [image: gae-fw.png]
>>>
>>>
>>>
>>> VPC firewall:
>>>
>>> [image: vpc-fw.png]
>>> Note that the VPC FW rule does apply to the GAE.
>>>
>>> WDYT?
>>>
>>> Also, we're currently looking into using IAP for securing our endpoints. 
>>> Is that the recommended way to implement authenticated communication 
>>> between GAE services?
>>>
>>> David
>>>
>>>
>>> On Monday, February 25, 2019 at 7:56:55 PM UTC+1, George (Cloud Platform 
>>> Support) wrote:

 It is not immediately apparent, after reading the documentation page 
 you link to, how certain IPs are to be whitelisted; targeted HTTP 
 requests, 
 service accounts, and Cloud Pub/Sub are mentioned, are recommended 
 solutions on that page. 

 The firewall configuration page stipulates, for requests received in 
 the flexible environment: 0.1.0.40 and 10.0.0.1. You need to create two 
 firewall rules to allow requests:

 0.1.0.40 - A rule to allow backend_flex to receive URL Fetch requests 
 from backend_std.
 10.0.0.1 - A rule to allow the service-to-service communication for the 
 URL Fetch requests in backend_flex.

>>>

-- 
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/d2e64390-8544-4b6f-b5cd-00fe318a3d42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Practical difference from Cloud Run

[Gabriel Axel]

Greetings. I watched the videos and read the docs of the new Cloud Run 
service and also took a look at the comparison table between GAE and Cloud 
Run, and to my understanding Cloud Run covers everything GAE Standard and 
Flexible do without any of their limitations. Maybe the only thing GAE "has 
over" Cloud Run is not having to write Dockerfile (except for Flexible 
custom runtime). Did I miss anything? Once Cloud Run goes GA, what use 
cases would be preferable for GAE over it?

-- 
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/df3597aa-4854-4850-8568-e9c0e74902cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How long will the original App Engine SDK (Python 2.7) be supported?

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

Hello Mark, 

Your concerns are fully justified, and, in fact, shared by quite a few 
developers. You needn't fear for the Python 2.7 apps already deployed. 2020 
is not as critical a date as may appear at first sight. Python 2.7 will get 
support for the benefit of existing Google App Engine (GAE) customers using 
Python 2.7 well beyond this date. 

Everyone is equally aware of difficulties faced by those who migrate a 
Python 2.7 GAE application to the 3.x series. Quite a few tools and 
infrastructure adjustments will facilitate this task, so developers should 
not feel too concerned. A smooth transition is in everyone's interest. 

-- 
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/6e427865-b816-4d80-ae6d-90d73e63507a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How does Codelabs work during the Google I/O extended events ?

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

Hi Fagbohun,

For this kind of queries I would suggest to use one of the Google I/O 
social media channels, you can choose between Facebook 
 , Twitter 
 or Google Developers’s blog 
.

I also found this presentation 

 
which is the official Google I/O Extended 2019 Organizer guide which may be 
helpful for you.

Have a great day!


On Tuesday, April 9, 2019 at 12:52:41 PM UTC-4, Fagbohun Omotayo wrote:
>
> Hello, The Google I/O is happening on the 7th of May 2019, I will like to 
> organise an extended event in my city, During the Google I/O extended 
> event, I learnt there will be a Codelab as part of the agenda, The Codelab 
> is a fun programming exercise. I will like to experiment with different 
> exercises during the codelabs, Can you please share with me, exercise ideas 
> for the Codelabs that is perfect for a Google I/O extended event putting 
> into consideration timing,which is short.
>

-- 
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/8aee503e-a266-4206-a4a4-3b189e400881%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Contacts pop-up issue

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

Hi Luke,

I understand your issue with Google Contacts however as my colleague George 
mentioned this is not the right channel to address this concern, please 
refer to this page to obtain proper assistance.

Thanks for your understanding.


On Wednesday, April 10, 2019 at 10:43:43 AM UTC-4, Luke Douglas wrote:
>
> The problem with reproducing the problem I'd you obviously do not have an 
> extensive Note field. I used the Note fueld extensively as well as I 
> maintain multiple fields. 
>
> If I open a single contact with just a few fields, the popup details is 
> responsive. 
>
> I NEVER had this issue with the classic full page view. 
>
> I don't mind Google developers wanting to show off their awesomeness but 
> when it interferes with my time. Then I have an issue. 
>
> Again, the removal of an option to use the classic view, which they did 
> provide during a transitional period, was simply a terrible decision. 
>
>

-- 
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/ac47d727-703c-4dac-a778-bf11c90643d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Hong Kong GPU Availability

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

Hello Derek, 

The importance of the Hong Kong zone is undeniable, and efforts are being 
made to provide the GPU-related service for the region. Still, there is as 
yet no clearly defined availability date. Generally, these zonal product 
launches are not normally made publicly known in advance, and this for 
various reasons, not least the likely delays occurring in the last hours. 
There are many factors contributing to a successful launch. Meanwhile, your 
patience is highly appreciated. 

-- 
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/97cba176-0066-4256-809c-98c03f1a0d9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Contacts pop-up issue

[Luke Douglas]

The problem with reproducing the problem I'd you obviously do not have an 
extensive Note field. I used the Note fueld extensively as well as I maintain 
multiple fields. 

If I open a single contact with just a few fields, the popup details is 
responsive. 

I NEVER had this issue with the classic full page view.

I don't mind Google developers wanting to show off their awesomeness but when 
it interferes with my time. Then I have an issue.

Again, the removal of an option to use the classic view, which they did provide 
during a transitional period, was simply a terrible decision.

-- 
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/bc9f0b0c-dea1-428d-b932-002fe32964d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: AppEngine Flex - Correct Firewall Configuration For Inter-Service-Communication

[dvd gsng]

Hi Nicolas, thanks for verifying our results. We think that the GAE 
documentation should be updated to reflect these restrictions more 
explicitly, are you in a position to forward this to the appropriate team 
by any chance?

Thanks
David


On Wednesday, April 3, 2019 at 7:38:12 PM UTC+2, Nicolas (Google Cloud 
Platform Support) wrote:
>
> Hi,
>
> Thanks for the screenshots! I’ve reproduced this and was able to confirm 
> that if you switch the App Engine Firewall rules to “Deny All” and then try 
> to granularly allow some IP address the app will return 403s. 
>
> This is most likely due to the internal App Engine infrastructure so I 
> would recommend IAP as your best current solution to communicate between 
> GAE services.
>
>
> On Wednesday, February 27, 2019 at 10:20:33 AM UTC-5, dvd gsng wrote:
>>
>> Hi George, thanks for replying. Unfortunately, we've tried that, but it 
>> didn't work out as expected. We added those two IPs (and two more, see 
>> initial post) to the GAE firewall as well as the regular VPC firewall. 
>> Please have a look that the images for reference:
>>
>> GAE firewall:
>>
>> [image: gae-fw.png]
>>
>>
>>
>> VPC firewall:
>>
>> [image: vpc-fw.png]
>> Note that the VPC FW rule does apply to the GAE.
>>
>> WDYT?
>>
>> Also, we're currently looking into using IAP for securing our endpoints. 
>> Is that the recommended way to implement authenticated communication 
>> between GAE services?
>>
>> David
>>
>>
>> On Monday, February 25, 2019 at 7:56:55 PM UTC+1, George (Cloud Platform 
>> Support) wrote:
>>>
>>> It is not immediately apparent, after reading the documentation page you 
>>> link to, how certain IPs are to be whitelisted; targeted HTTP requests, 
>>> service accounts, and Cloud Pub/Sub are mentioned, are recommended 
>>> solutions on that page. 
>>>
>>> The firewall configuration page stipulates, for requests received in the 
>>> flexible environment: 0.1.0.40 and 10.0.0.1. You need to create two 
>>> firewall rules to allow requests:
>>>
>>> 0.1.0.40 - A rule to allow backend_flex to receive URL Fetch requests 
>>> from backend_std.
>>> 10.0.0.1 - A rule to allow the service-to-service communication for the 
>>> URL Fetch requests in backend_flex.
>>>
>>

-- 
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/cbac43eb-e50d-4180-9001-3547771f1c82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: encoded keys in the app vs datastore viewer

[Joshua Fox]

I don't know how to make them use the same encoding.

To parse the different formats, either use various Google libraries -- see
for example this Pull Request
https://github.com/googleapis/google-cloud-python/pull/3491  -- or else
write your own code. For this, the Protobuf "proto" file is needed, so
either dig that up from some source code, like this, or else "roll your
own" (not easy) by  reverse-engineering the Protobuf binaries. Not easy.

Note that  project-id, though part of this URL-safe string, is not really
relevant to the Key itself.  For example, if you copy objects between GAE
projects, you want to access the "same" object in the two projects using
the same query, ignoring the project.

On Tue, Apr 9, 2019 at 7:27 PM dir Ls  wrote:

> I took the key in the datastore viewer and used the
> google.appengine.ext.ndb.Key(urlsafe=) api and I see it reconstructs the
> key properly with the kind and id. In addition, I see an app field for the
> key. But in the golang representation the Key struct doesn't have an app
> field. So if an app has multiple micro services one in golang and another
> in Python, and the encoded value is generated in one microservice and
> passed to another, will there be a problem? Is it possible to make them all
> use the same encoding?
>
> On Sunday, April 7, 2019 at 3:16:05 PM UTC-7, George (Cloud Platform
> Support) wrote:
>>
>> The string representation of a key looks cryptic, but is not
>> encrypted. If you don't want to expose this data to your users, you may
>> consider encrypting these strings.
>>
>> How do your app keys look like in your app, and why do you consider these
>> keys encrypted? A screen capture, with personal data highlighted out, would
>> help in this case, as for Datastore viewer. You may refer to the "Key
>> Class" documentation page
>> 
>> for related information.
>>
> --
> 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/8523691e-afcf-48ae-bde4-9a66ed5a636e%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 


*JOSHUA FOX*
Director, Software Architecture | Freightos



*T (Israel): *+972-545691165 | *T (US)*:  +1-3123400953
Smooth shipping.

-- 
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/CAD%3DB7cPt4C_FF%2BEpVSmrJHtTAnr%2BppXrMWg%3DQMXyJo-urNrABQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: What does X-Google-Apps-Metadata: domain=gmail mean?

[Joshua Fox]

I do not use Namespace API, Users API, or Google-provided Authentication.

So if I understand correctly, GAE adds these  headers "just in case", but
they are irrelevant to me.

On Tue, Apr 9, 2019 at 8:35 PM ykarout via Google App Engine <
google-appengine@googlegroups.com> wrote:

> Hello Joshua,
>
> From doing some internal research:
>
> 1- X-AppEngine-Default-Namespace is the default namespace used by the 
> Namespace
> API .
> It is only used for domain-restricted authentication. If your app is
> available to all gmail.com users, then it should be gmail.com unless a
> custom domain is specified.
>
> 2- X-Google-Apps-Metadata is used by the Users API
> 
> to specify a Google Apps domain. For normal Google login, it is set to
> gmail.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 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/91d74baf-215d-4b89-a987-7b7dbb3bc80e%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 


*JOSHUA FOX*
Director, Software Architecture | Freightos



*T (Israel): *+972-545691165 | *T (US)*:  +1-3123400953
Smooth shipping.

-- 
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/CAD%3DB7cMOYpA0S5zGXb5_znza%2BxUgGhAeye2vy-ExX4ytYDO6hQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.