I've been successfully deploying my node.js GAE web app for months using gcloud app deploy. It's been a month or so since my last deployment and I've made a few updates since then that I want to get out. So I did my usual

gcloud app deploy

and it uploaded the files and then failed, giving me this error:

(gcloud.app.deploy) Error Response: [5] failed to getGaiaID for "<SERVICE NAME WAS HERE"": generic::not_found: Account disabled: 810593457260

At first I thought it was a payment issue - but my payment info is up to date. The only major change to the code I recall is that between this deploy and the last deployment, I started versioning the project with git and pushing to github.

Does anyone have any ideas? In particular, is there any reason Git or GitHub .git would interfere with a gcloud deployment?

Thanks

CodePudding user response：

So, oddly enough, my account ended up not being disabled. My last three attempts at deploying all occurred at unsecured network locations (airport, hotel, convention center). Apparently, Google gives a disabled account warning when you try to deploy over an unsecure network

Therefore the command gcloud app deploy will not be successful when performed over an unsecure internet network.

Later, attempting to make a deploy over unsecure networks disabled the project in GAE. Since billing was in good standing, they continued to serve my content (and bill for it) but changes to the service were disabled.

To enable them again, follow the instructions:

To enable a service account, at minimum the user must be granted the Service Account Admin role (roles/iam.serviceAccountAdmin) or the Editor basic role (roles/editor)

1. In the Cloud Console, go to the Service accounts page.
2. Select the project
3. Click the name of the service account that you want to enable
4. Under Service account status, click Enable service account, then click Enable to confirm the change.

Other resources:

• How to understand the service accounts
• How to create and manage service accounts