Re: [google-appengine] login: admin in python37

[Joshua Smith]

I'm hoping someone on this list has encountered this, and can say "Yeah, I ran 
into that. Here's how I dealt with it..."

I'm looking for an easy step-by-step guide to just get the exact behavior that 
Python 2.7 had.

-Joshua

> On Jan 25, 2021, at 1:05 PM, 'Elliott (Cloud Platform Support)' via Google 
> App Engine  wrote:
> 
> Hello Joshua,
> 
> I understand that you would like an easy way to implement authentication 
> because you may not continue to use login: admin. I was able to confirm this. 
> First, I would like to apologize for the inconvenience. There is no easy way 
> other than to implement one of the options listed in this document 
> .
> 
> You are presented with some options including Firebase Authentication, Google 
> Sign-In and OAuth 2.0 and OpenID Connect. Each of these technologies are 
> described in the document.
> 
> I would like your thoughts on the recommended ways so that we may find a 
> solution that agrees with you.
> 
> I hope that we may now have enough to elaborate on this discussion.
> 
> 
> On Friday, January 22, 2021 at 1:07:16 PM UTC-5 Joshua Smith wrote:
> In my quest to figure out how to keep using Google App Engine when Python27 
> eventually goes away, I've just run into yet another case where something 
> simple seems to have been replaced with a nightmare of complexity 
> .
> 
> In my old app.yaml, I had this:
> 
> - url: /admin/.*
>   script: main.app
>   secure: always
>   login: admin
> 
> Unfortunately, python37 doesn't support login: admin any more (!). I'm facing 
> a mountain of documentation detailing a bunch of different ways I can do 
> authentication now.
> 
> Stack overflow is no help at all in simplifying this.
> 
> Anyone here have advice on the easiest possible way to get the old Python27 
> behavior that you have to be logged in as the app administrator in order to 
> hit a certain URL?
> 
> This isn't for ensuring crons are only run by cron. That seems pretty easy by 
> looking at headers.
> 
> This is for when you have administrative functions that only the developers 
> need access to, and I'm looking for the easiest way to ensure a URL is only 
> accessible to those particular people.
> 
> In case it matters, I'm using Flask.
> 
> -Joshua
> 
> 
> -- 
> 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/05ac62c4-6c44-4e7b-8068-1601d6a4eef0n%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/90827D18-4CCA-407F-92D4-3C2485FC0EBE%40gmail.com.

[google-appengine] Re: login: admin in python37

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

Hello Joshua,

I understand that you would like an easy way to implement authentication 
because you may not continue to use login: admin. I was able to confirm 
this. First, I would like to apologize for the inconvenience. There is no 
easy way other than to implement one of the options listed in this document 

.

You are presented with some options including Firebase Authentication, 
Google Sign-In and OAuth 2.0 and OpenID Connect. Each of these technologies 
are described in the document.

I would like your thoughts on the recommended ways so that we may find a 
solution that agrees with you.

I hope that we may now have enough to elaborate on this discussion.


On Friday, January 22, 2021 at 1:07:16 PM UTC-5 Joshua Smith wrote:

> In my quest to figure out how to keep using Google App Engine when 
> Python27 eventually goes away, I've just run into yet another case where 
> something simple seems to have been replaced with a nightmare of 
> complexity 
> 
> .
>
> In my old app.yaml, I had this:
>
> - url: /admin/.*
>   script: main.app
>   secure: always
>   login: admin
>
> Unfortunately, python37 doesn't support *login: admin* any more (!). I'm 
> facing a mountain of documentation detailing a bunch of different ways I 
> can do authentication now.
>
> Stack overflow is no help at all in simplifying this.
>
> Anyone here have advice on the *easiest possible way* to get the old 
> Python27 behavior that you have to be logged in as the app administrator in 
> order to hit a certain URL?
>
> This isn't for ensuring crons are only run by cron. That seems pretty easy 
> by looking at headers.
>
> This is for when you have administrative functions that only the 
> developers need access to, and I'm looking for the easiest way to ensure a 
> URL is only accessible to those particular people.
>
> In case it matters, I'm using Flask.
>
> -Joshua
>
>

-- 
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/05ac62c4-6c44-4e7b-8068-1601d6a4eef0n%40googlegroups.com.

[google-appengine] Re: Issues accessing backend API deployed in App Engine

['Daniel (Google Cloud Support)' via Google App Engine]

That error message usually points out that your application starting a 
webserver and handling requests correctly [1]. There is an example on how 
to deploy a Springboot application for Google App Engine Java 11 runtime 
here [2] (the repository is here [3]). I'd strongly advise you to check [2] 
and [3] and most importantly make sure that your application is running 
locally without any issues [4] prior to deploying to App Engine.

[1] 
https://cloud.google.com/appengine/docs/standard/java11/how-requests-are-handled#handling_requests
[2] https://cloud.google.com/appengine/docs/standard/java11/quickstart
[3] 
https://github.com/GoogleCloudPlatform/java-docs-samples/tree/master/appengine-java11/springboot-helloworld
[4] 
https://cloud.google.com/appengine/docs/standard/java11/testing-and-deploying-your-app
On Monday, January 25, 2021 at 11:05:40 AM UTC+1 song...@gmail.com wrote:

> Hi,
>
> After further investigation, i saw the following error in the logs
>
> *"Start program failed: failed to detect app after start: 
> ForAppStart(): [aborted, context canceled. subject:\"app/valid\" 
> Timeout:30m0s, attempts:119980 aborted, context canceled. 
> subject:\"app/invalid\" Timeout:30m0s, attempts:119997]",*
>
> Greatly appreciate if anyone could give insights on this error. THanks!
>
> On Tuesday, January 12, 2021 at 12:07:42 AM UTC+8 Elliott (Cloud Platform 
> Support) wrote:
>
>> Hello,
>>
>> I understand that when you are placing a request using postman, it 
>> remains in “sending request” for a long time.
>>
>> I am unable to find a common issue at this time that would cause the 
>> behavior you are describing. Also, Google Groups is meant for general 
>> discussions.
>>
>> To move this along and narrow down the focus, I would suggest while 
>> sending your request, open Postman Console (View > Show Postman Console), 
>> resend the request and check for any error logs in the console. 
>>
>> This way, we will be able to get extra information that may help isolate 
>> the problem.
>>
>>
>> On Monday, January 11, 2021 at 9:16:40 AM UTC-5 song...@gmail.com wrote:
>>
>>> Hi All,
>>>
>>> I have a set of Backend springboot application deployed successfully 
>>> deployed in the APP engine. However, when i tried to access the one of the 
>>> backend API in the postman, the request does not return, the postman 
>>> remains in "sending request" for a long time.
>>>
>>> As you can see from the GCP logs below, my backed service is running.
>>>
>>> May i know if anyone encounter the same issue before whereby the service 
>>> is deployed successfully in the APP engine, but request cannot be made and 
>>> no timeout is thrown either. 
>>>
>>> Thanks in advance!
>>>
>>> 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/bf9bcdc0-adff-4ae8-b104-4a8615772821n%40googlegroups.com.

[google-appengine] Re: Push tasks "starting late"

['verges' via Google App Engine]

Hello,

On one hand, please note that the documentation 
 
specifies that there's no time delivery guarantee for push tasks. It is 
possible that some tasks are delivered lately than what the average task 
usually takes, which is not an unexpected behavior for push tasks.

On the other hand, I'd like to mention that push tasks are a legacy App 
Engine service which is no longer recommended. The functionality offered by 
push tasks has been superseded by Task Queues and the migration would be 
required as soon as you update to the newer App Engine runtimes. I would 
recommend having a look at this page 

 
which explain how to approach the migration process.
On Sunday, January 24, 2021 at 11:43:44 AM UTC+1 Rob Curtis wrote:

> Found that delayed starts are happening mostly for transactional task 
> adds. 
> This is code that's unchanged and only happening in one project. Any ideas?
>
>
> On Sunday, January 24, 2021 at 7:22:04 AM UTC+2 Rob Curtis wrote:
>
>> Hi, 
>>
>> I'm experiencing an issue on 1 appengine project where push tasks are 
>> taking a really long time to start executing. The tasks that take long also 
>> don't show in the console.
>> Other projects that share the same code base are not experiencing the 
>> issue.
>> Queues and instances are configured the same between the projects. The 
>> projects have low load.
>>
>> Some examples:
>> A task with no defined eta (i.e. it should just run as soon as it can) 
>> can  run up to *56minutes later. *Majority of the "late starters" seem 
>> be around 5 minutes late.
>> I get that push queue tasks will run when they get  the opportunity, but 
>> this is a bit extreme (and I've never seen it happening before).
>>
>> *Is anyone else experiencing this was push tasks at the moment?*
>>
>> Thanks
>> Rob
>>
>>
>>
>>
>>
>>
>>

-- 
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/ef73ceae-e276-4366-9924-b0cf58e20fb1n%40googlegroups.com.

[google-appengine] Re: Modify Datastore Admin Backup Built-in Taskqueue

[Brenshield Abanid]

Hi Elliot,

Thank you for the answer. Unfortunately I can't provide the documentation 
that I was talking about since I just saw it on the thread on 
stackoverflow. I thought the answer was based on the documentation but it 
was not. Sorry for that.

Like you said, you can pass a parameter based on this thread 
: but is there any documentation 
indicating on what other parameters you can pass? Because if there's any, 
can you please provide a link? Thank you so much!
On Wednesday, January 20, 2021 at 4:08:48 AM UTC+8 Elliott (Cloud Platform 
Support) wrote:

> Hello,
>
> I understand that you to want to export the data from Cloud Datastore that 
> has a specific date range you that may specify programmatically such as the 
> example:
>
>
> /_ah/datastore_admin/backup.create?name=MyBackup&StartDate=12-01-20&EndDate=01-12-21
>
> I did some research into this and found that the backup URL is meant to be 
> done automatically. I was wanting to share some documentation available to 
> the public on the details but since this is not standard, examples are 
> limited. So to evolve this conversation and provide advice to you, can you 
> please provide the documentation you found to illustrate your use case?
>
> I have found that it may be possible to use the URL with parameters 
> ,
>  
> but I am unable to verify this using official documentation. So it may not 
> work.
>
>
> I have looked at Cloud Datastore Admin as an option but it is deprecated 
> .
>  
> I would suggest looking into the new method of exporting as backup 
> .
>
> To add value to this thread, I was able to find a thread with an accepted 
> answer relating to a similar question 
> 
>  
> indicating the Cloud Datastore Admin is deprecated and that upgrading to 
> the Cloud Datastore export service was recommended.
>
> I hope this helps.
>
>
> On Tuesday, January 19, 2021 at 10:10:50 AM UTC-5 ray.a...@gmail.com 
> wrote:
>
>> Hello everyone,
>>
>> I have some questions regarding the datastore backup. I'm wondering if we 
>> can modify or override the built-in task queue on datastore admin 
>> */_ah/datastore_admin/backup.create?*
>>
>> What I want to do when exporting the data from datastore is that I would 
>> only need to export the data that has specific date range that I specify. I 
>> saw on the documentation that you can pass a parameter to the URL. Is its 
>> possible to pass the parameter on the date range like this one?
>>
>> */_ah/datastore_admin/backup.create?name=MyBackup&StartDate=12-01-20&EndDate=01-12-21.*
>>
>> Please let me know if I miss something.
>>
>> Thanks a lot
>> Ray
>>
>

-- 
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/7c598f89-8c74-45c1-9d68-09ee8c1e19c8n%40googlegroups.com.

[google-appengine] Re: Issues accessing backend API deployed in App Engine

[ks songs]

Hi,

After further investigation, i saw the following error in the logs

*"Start program failed: failed to detect app after start: 
ForAppStart(): [aborted, context canceled. subject:\"app/valid\" 
Timeout:30m0s, attempts:119980 aborted, context canceled. 
subject:\"app/invalid\" Timeout:30m0s, attempts:119997]",*

Greatly appreciate if anyone could give insights on this error. THanks!

On Tuesday, January 12, 2021 at 12:07:42 AM UTC+8 Elliott (Cloud Platform 
Support) wrote:

> Hello,
>
> I understand that when you are placing a request using postman, it remains 
> in “sending request” for a long time.
>
> I am unable to find a common issue at this time that would cause the 
> behavior you are describing. Also, Google Groups is meant for general 
> discussions.
>
> To move this along and narrow down the focus, I would suggest while 
> sending your request, open Postman Console (View > Show Postman Console), 
> resend the request and check for any error logs in the console. 
>
> This way, we will be able to get extra information that may help isolate 
> the problem.
>
>
> On Monday, January 11, 2021 at 9:16:40 AM UTC-5 song...@gmail.com wrote:
>
>> Hi All,
>>
>> I have a set of Backend springboot application deployed successfully 
>> deployed in the APP engine. However, when i tried to access the one of the 
>> backend API in the postman, the request does not return, the postman 
>> remains in "sending request" for a long time.
>>
>> As you can see from the GCP logs below, my backed service is running.
>>
>> May i know if anyone encounter the same issue before whereby the service 
>> is deployed successfully in the APP engine, but request cannot be made and 
>> no timeout is thrown either. 
>>
>> Thanks in advance!
>>
>> 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/d3d40cbd-48d6-4e9f-9aa0-ee353cc37318n%40googlegroups.com.