[google-appengine] Process to Authenticate WebAPI of GAE

[udit sharma]

Hey All, 

I have an application running using Firebase and GAE. Using firebase to 
authenticate users and GAE to deploy the backend logic code. Firebase 
Real-time database is acting as a database for us. Calls between GAE and 
Firebase database is happening using Firebase Database Secrets. I have 
created WebAPI which my application front end is using for data 
requirements. My API is public now, anyone with the URL can call it and get 
the result. Though the user authentication is happening using Firebase 
OAuth, the API can be used by anyone who gets to know the parameters and 
endpoints. I want to secure my WebAPI that can only be used by the 
application and some specific IP address for testing purpose. 

What shall I use to secure that? Firebase uuid which is unique to the 
specific users?  if anyone gets that uuid of his account ( anyhow ) it 
won't be secured. 
Any other way to secure that?

Any help would be appreciated!

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 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/12ac4096-026a-42d7-ad4b-9d541e4c25eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Unable to update app engine app

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

I would like to encourage you to file a Public Issue Tracker 
 report any time you 
see an unexpected behavior on the Cloud Platform as well.

You could use the “gcloud app deploy” command with the “--verbosity=debug” 
and also “gcloud info” with --anonymize parameter to provide us the stack 
trace and your information about the current gcloud environment there, so 
that we would be able to investigate the issue root cause efficiently.


On Thursday, March 8, 2018 at 3:25:04 PM UTC-5, Nezare Chafni wrote:
>
> I can't update my app engine app This happened several times since 
> moving from the appcfg to the new SDK, and its insanely annoying. I tried 
> everything. even sanity check debug statements. It's annoying enough to not 
> make me wanna use app engine again.
>
> I tried new versions, overwriting versions, skipping files, removing pyc, 
> almost everything I can think!
>
> Any ideas? Is this happening to anyone else?!
>
>
>

-- 
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/71d508a7-9573-4b50-816f-9d84b4a112e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Delpoy BUG - can't update my app

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

I see that you have created a duplicate thread 
 
about this issue. All further communications will occur in your duplicate 
thread 
.

-- 
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/b5e2099b-2e0e-42e7-94a6-fd6b757f2c34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Unable to update app engine app

[Ani Hatzis]

Well, no, I had no such issue, but that doesn't mean anything. You could 
file a bug report on their public issue tracker 

.

All the best


On Thursday, 8 March 2018 22:53:48 UTC+1, Nezare Chafni wrote:
>
> I've been using the new SDK for 6 months, nothing special, the problem 
> started with the switch is what I'm saying. Everything succeeds, no errors, 
> my code just never updates.
>
> app.yaml is configured correctly, again, i've been deploying this app with 
> the new sdk. the configuration is correct.
>
> This is a bug on app engine's side, the update goes through successfully 
> the code just never updates. I've tried everything.
>
>
>
> On Thursday, March 8, 2018 at 1:36:48 PM UTC-8, Ani Hatzis wrote:
>>
>> When I used App Engine SDK (appcfg) it could happen that a deployment 
>> failed, so I repeated the deployment a few minutes later. The same is with 
>> Cloud SDK (cloud app deploy). Nothing noteworthy. The new SDK has a little 
>> learning curve, but I believe it is far superior to the App Engine SDK.
>>
>> However, you haven't actually explained what you tried and what exactly 
>> fails. Do you get a time-out, an error message or something? Or what 
>> environment do you use? Does your app have multiple services or just the 
>> default service? Has it worked before with cloud app deploy or is it 
>> your first attempt to deploy with the new SDK? What are your exact steps?
>>
>> Since you asked for ideas: Two things that I first stumbled over as a 
>> long-time appcfg user:
>>
>>1. When you have never deployed before with the new SDK: Beside a 
>>correct gcloud initialization, login and configuration, you would also 
>> need 
>>to remove the version and the app ID from the app.yaml file. The command 
>>will complain about these two if present, but possible to miss the error 
>> I 
>>guess.
>>2. If you already have used the new SDK to deploy successfully: In 
>>gcloud, have you switched to the configuration that has the correct 
>> project 
>>ID and account before you deploy? (gcloud config configurations list 
>>will show you the active configuration and properties)
>>
>> If your problem persists, I suggest to ask on Stack Overflow with more 
>> details though, unless of course it turns out to be an issue specific to 
>> your account or project.
>>
>> Good luck!
>> Ani
>>
>>
>> On Thursday, 8 March 2018 21:25:04 UTC+1, Nezare Chafni wrote:
>>>
>>> I can't update my app engine app This happened several times 
>>> since moving from the appcfg to the new SDK, and its insanely annoying. I 
>>> tried everything. even sanity check debug statements. It's annoying enough 
>>> to not make me wanna use app engine again.
>>>
>>> I tried new versions, overwriting versions, skipping files, removing 
>>> pyc, almost everything I can think!
>>>
>>> Any ideas? Is this happening to anyone else?!
>>>
>>>
>>>

-- 
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/d42e6d90-c66d-494c-9c7f-bc1c80da8c63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Unable to update app engine app

[Nezare Chafni]

I've been using the new SDK for 6 months, nothing special, the problem 
started with the switch is what I'm saying. Everything succeeds, no errors, 
my code just never updates.

app.yaml is configured correctly, again, i've been deploying this app with 
the new sdk. the configuration is correct.

This is a bug on app engine's side, the update goes through successfully 
the code just never updates. I've tried everything.



On Thursday, March 8, 2018 at 1:36:48 PM UTC-8, Ani Hatzis wrote:
>
> When I used App Engine SDK (appcfg) it could happen that a deployment 
> failed, so I repeated the deployment a few minutes later. The same is with 
> Cloud SDK (cloud app deploy). Nothing noteworthy. The new SDK has a little 
> learning curve, but I believe it is far superior to the App Engine SDK.
>
> However, you haven't actually explained what you tried and what exactly 
> fails. Do you get a time-out, an error message or something? Or what 
> environment do you use? Does your app have multiple services or just the 
> default service? Has it worked before with cloud app deploy or is it your 
> first attempt to deploy with the new SDK? What are your exact steps?
>
> Since you asked for ideas: Two things that I first stumbled over as a 
> long-time appcfg user:
>
>1. When you have never deployed before with the new SDK: Beside a 
>correct gcloud initialization, login and configuration, you would also 
> need 
>to remove the version and the app ID from the app.yaml file. The command 
>will complain about these two if present, but possible to miss the error I 
>guess.
>2. If you already have used the new SDK to deploy successfully: In 
>gcloud, have you switched to the configuration that has the correct 
> project 
>ID and account before you deploy? (gcloud config configurations list 
>will show you the active configuration and properties)
>
> If your problem persists, I suggest to ask on Stack Overflow with more 
> details though, unless of course it turns out to be an issue specific to 
> your account or project.
>
> Good luck!
> Ani
>
>
> On Thursday, 8 March 2018 21:25:04 UTC+1, Nezare Chafni wrote:
>>
>> I can't update my app engine app This happened several times 
>> since moving from the appcfg to the new SDK, and its insanely annoying. I 
>> tried everything. even sanity check debug statements. It's annoying enough 
>> to not make me wanna use app engine again.
>>
>> I tried new versions, overwriting versions, skipping files, removing pyc, 
>> almost everything I can think!
>>
>> Any ideas? Is this happening to anyone else?!
>>
>>
>>

-- 
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/e57eb893-85c2-470d-ae49-22075fdc4e18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Unable to update app engine app

[Ani Hatzis]

When I used App Engine SDK (appcfg) it could happen that a deployment 
failed, so I repeated the deployment a few minutes later. The same is with 
Cloud SDK (cloud app deploy). Nothing noteworthy. The new SDK has a little 
learning curve, but I believe it is far superior to the App Engine SDK.

However, you haven't actually explained what you tried and what exactly 
fails. Do you get a time-out, an error message or something? Or what 
environment do you use? Does your app have multiple services or just the 
default service? Has it worked before with cloud app deploy or is it your 
first attempt to deploy with the new SDK? What are your exact steps?

Since you asked for ideas: Two things that I first stumbled over as a 
long-time appcfg user:

   1. When you have never deployed before with the new SDK: Beside a 
   correct gcloud initialization, login and configuration, you would also need 
   to remove the version and the app ID from the app.yaml file. The command 
   will complain about these two if present, but possible to miss the error I 
   guess.
   2. If you already have used the new SDK to deploy successfully: In 
   gcloud, have you switched to the configuration that has the correct project 
   ID and account before you deploy? (gcloud config configurations list 
   will show you the active configuration and properties)

If your problem persists, I suggest to ask on Stack Overflow with more 
details though, unless of course it turns out to be an issue specific to 
your account or project.

Good luck!
Ani


On Thursday, 8 March 2018 21:25:04 UTC+1, Nezare Chafni wrote:
>
> I can't update my app engine app This happened several times since 
> moving from the appcfg to the new SDK, and its insanely annoying. I tried 
> everything. even sanity check debug statements. It's annoying enough to not 
> make me wanna use app engine again.
>
> I tried new versions, overwriting versions, skipping files, removing pyc, 
> almost everything I can think!
>
> Any ideas? Is this happening to anyone else?!
>
>
>

-- 
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/60e1e57e-02ac-466e-b1a3-01a5c7a775f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Unable to update app engine app

[Nezare Chafni]

I can't update my app engine app This happened several times since 
moving from the appcfg to the new SDK, and its insanely annoying. I tried 
everything. even sanity check debug statements. It's annoying enough to not 
make me wanna use app engine again.

I tried new versions, overwriting versions, skipping files, removing pyc, 
almost everything I can think!

Any ideas? Is this happening to anyone else?!


-- 
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/47bd63ee-5006-4332-8825-07e793956228%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Delpoy BUG - can't update my app

[Nezare Chafni]

I can't update my app, 5th time it happens to me since moving to the new 
sdk from appcfg! the app just won't update, did several sanity 
print statements and added dummy functionality just to make sure, been an 
app engine user for years and this makes me never wanna use it again, been 
blocked for over 24 hours because of this!

-- 
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/a6fc7e8e-3551-4239-932b-2f351483b921%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: gcloud vs. goapp for GO appengine

[chalbert via Google App Engine]

I discovered that currently, gcloud does not support vendored dependencies, 
so efforts to restructure our repository have stopped. We are still using 
my goapp script to do deploys.

Recently, on 2018-03-01, Homebrew renamed python3 to python, breaking my 
goapp script, so here is a fix:
#!/bin/bash
gcloud="$(which gcloud)"
[ -L "$gcloud" ] && gcloud="$(readlink "$gcloud")"
appdir="$(dirname "$(dirname "$gcloud")")"
goapp="${appdir}/platform/google_appengine/goapp"
if ! [ -f "$goapp" ]; then
echo "goapp is not in the Google Cloud SDK libraries." >&2
echo "Hint: try running this command:" >&2
echo "" >&2
echo "gcloud components install app-engine-go" >&2
fi
# On 2018-03-01, Homebrew renamed python3 to python, breaking scripts that 
expected
# python to be 2.7. Make sure we are using Python 2.
if [[ "$(python --version 2>&1)" == *' 2.7'* ]]; then
PYTHON=python
elif type python2.7 &>/dev/null; then
PYTHON=python2.7
elif type python2 &>/dev/null; then
PYTHON=python2
elif [[ "$(/usr/local/opt/python@2/bin/python --version 2>&1)" == *' 2.7'* 
]]; then
PYTHON=/usr/local/opt/python@2/bin/python
elif [[ "$(/usr/bin/python --version 2>&1)" == *' 2.7'* ]]; then
PYTHON=/usr/bin/python
else
echo "could not find Python 2.7 at python, python2.7, python2, or 
/usr/bin/python" >&2
exit 1
fi
"$PYTHON" "$goapp" "$@"


On Monday, October 2, 2017 at 1:02:58 PM UTC-7, chal...@evernote.com wrote:
>
> My main concern is, what is going to happen to goapp test? This is a 
> critical part of our toolchain that tests our code under appengine go (as 
> opposed to non-appengine go, which I installed via brew). I am not seeing a 
> documented replacement for this tool anywhere.
>
> As a temporary hack to keep access to goapp, I created a wrapper script to 
> run the goapp script hidden inside the google-cloud-sdk distro. See 
> https://groups.google.com/forum/#!topic/google-appengine-go/h4GKKDAskxY
>
> Other than that, I am currently working to convert our project structure 
> to the new, more stringent one enforced by gcloud. The conversion is not 
> complete, and is rather involved. Interestingly, dev_appserver.py and goapp 
> deploy are more lax about project structure than gcloud deploy, in that 
> before, the app entry point (main.go) is was allowed to be inside the 
> GOPATH. I therefore set GOPATH to the repo root in order to exclude 
> external disturbances from our build, and put main.go inside a sibling to 
> the src directory. This breaks under gcloud deploy, since main.go is not 
> allowed to be anywhere under the GOPATH. (I had to read the SDK source code 
> to discover this.)
>
> To become compliant with gcloud expectations, I am working on relocating 
> main.go outside of the GOPATH, while keeping both a gopath directory and 
> main.go inside the same repository for simplicity (I don't want to have to 
> keep an app repo and our private library repos in sync).
>
> However, once that is done, I will still need a fast way to run unit tests 
> under appengine go before deploying. I hope there are plans to keep the 
> functionality of goapp test.
>
> On Tuesday, April 25, 2017 at 9:46:26 AM UTC-7, Justin Beckwith wrote:
>>
>> Hey folks,
>> Apologies for the confusion.  Here's what's happening.
>>
>> *We are trying to move towards a single Cloud SDK install.*  At the same 
>> time, we're trying not to break the existing App Engine SDK downloads.  We 
>> are headed towards a future (not far away) where everything gets wrapped up 
>> into https://cloud.google.com/sdk/.  Instead of having separate SDKs for 
>> Go/Python/Java/PHP, we want one toolchain.
>>
>> *We are moving towards tooling consistency.*  The goal is to make 
>> `gcloud app deploy` work for each language supported by App Engine.  With 
>> the exception of Java, we're mostly there.  You should be able to use 
>> `gcloud app deploy` and `dev_appserver.py .` instead of `goapp update ` or 
>> `goapp serve`.
>>
>> I'm interested in getting some feedback on this approach. Do you feel 
>> like `gcloud app deploy` and `dev_appserver.py .` are enough?  Or are there 
>> other reasons you want to keep using `goapp`?
>>
>> Is this just a matter of unclear documentation?
>>
>> Thanks!
>>
>>
>> On Tue, Apr 25, 2017 at 1:21 AM, Michael Amie  
>> wrote:
>>
>>> Tim,
>>>
>>> You are not insane. I have noticed this as well w/ respect to the 
>>> missing executable bit set on at least one of the goapps (and if I recall 
>>> correctly, when I looked into this a month or so ago), several other 
>>> scripts / binaries weren't set to executable as well, post-installation.
>>>
>>> As you mention, I got the impression the stand-along "go SDK" was being 
>>> phased out / deprecated and this was getting rolled into the cloud SDK as a 
>>> module / component for it.
>>>
>>> It seems like they didn't test the new installer or something before 
>>> rolling it out, and based on the combo of 1. The broken install and 2. The 
>>> doublespeak of the d