Although I'm not sure whether this is the right place to discuss the trouble-shooting, here some things to try. My apologies if I repeat things you already have tried.
1. cd into the directory, where the app.yaml file of your application is located 2. With the "." and the debug level (see gcloud Reference <https://cloud.google.com/sdk/gcloud/reference/>): gcloud beta app deploy . --verbosity=debug 3. Next the command will prompt you to confirm the deployment and shows a few values. In the first lines you should see values for "descriptor" and "source". "descriptor" should be the absolute path to the app.yaml file, and "source" to the parent directory of the app.yaml file. 4. The --verbosity=debug flag will also print more information (that otherwise is only written to the gcloud log file). It will show every file that is skipped and every file that is uploaded during deployment (with full paths). After the skipping part, the "Uploading ..." part should only mention 24 files or so: ╔════════════════════════════════════════════════════════════╗╠═ Uploading 1 file to Google Cloud Storage ═╣╚INFO: Uploading [/home/REDACTED/shipping-backend/app.yaml] to [8a185114176aa5cdd7b0e1233915bb2bf03aeb33] (Since it isn't my first deployment of your app it uploads just the one file that I have changed) The supposed 10,000 files would hopefully will show up here or right before that, and then you should get a better idea what is causing the error. This answer <https://stackoverflow.com/a/42471654/1549523> suggests to check the directory for hidden content (e.g. *.git*, *.venv*, anything from your IDE). This other answer <https://stackoverflow.com/a/42451932/1549523> suggests to check if you have (circular) symlinks in that directory. If you are 100% sure the directory contains only the 42 items that you have shared with me: 1. You can evaluate whether you have the same error if you don't use the beta command. For avoiding the Endpoints beta feature of a managed rollout strategy, we would need to change the app.yaml file as described in this Troubleshooting App Engine Flexible Deployment <https://cloud.google.com/endpoints/docs/openapi/troubleshoot-aeflex-deployment> . 2. Search for the current config_id of your deployed Endpoints API service gcloud endpoints services describe [PROJECT_ID].appspot.com 3. Very likely there is one serviceConfig. Copy the value of "id:", something like 2018-05-19r0 4. Add the value as config_id to your app.yaml and change the value of rollout_strategy from "managed" to "fixed", so it looks something like this: endpoints_api_service: name: "[PROJECT_ID].appspot.com" config_id: "2018-05-19r0" rollout_strategy: fixed # rollout_strategy: managed 5. Run the normal command: gcloud app deploy . --verbosity=debug There is still the probability that your gcloud installation or setup is "kaput", which you could verify with a new installation and setup as explained in Before you begin <https://cloud.google.com/endpoints/docs/openapi/get-started-app-engine#before-you-begin> in Cloud Endpoints > OpenAPI > Getting Started with Endpoints on App Engine Flexible Environment <https://cloud.google.com/endpoints/docs/openapi/get-started-app-engine>. If this doesn't help, then it might be a bug, and I would file a bug-report in the Public Issue Tracker <https://issuetracker.google.com/>. For any other trouble-shooting, I would recommend to create your own question on Stack Overflow. GCP support monitors certain tags, such as *google-app-engine*. Also include the output of gcloud version, and --maybe redacted for secrets and project IDs-- the output of gcloud info - Don't forget to a post the link to your question here, too. Good luck Ani On Sat, May 19, 2018 at 10:23 PM Esther Escobodo <[email protected]> wrote: > > > yes > > On Sat, May 19, 2018, 12:46 PM Esther Escobodo <[email protected]> > wrote: > >> >> >> yes >> >> On Sat, May 19, 2018, 12:45 PM Ani Hatzis <[email protected]> wrote: >> >>> Hey Lourdu Rajan, >>> >>> gcloud endpoints services deploy openapi.yaml >>> Everything fine as expected. >>> >>> gcloud beta app deploy >>> at some point confirmed the upload of 24 files: >>> ╔════════════════════════════════════════════════════════════╗╠═ >>> Uploading 24 files to Google Cloud Storage ═╣ >>> ╚════════════════════════════════════════════════════════════╝File >>> upload done.Updating service [default] (this may take several >>> minutes)...done. >>> >>> My understanding is that the error occurs before you get this message >>> right? >>> >>> However, the deploy fails later where it reads the Cloud SQL connection >>> (I don't have one yet, I'll fix this later). >>> ERROR: (gcloud.beta.app.deploy) Error Response: [13] Invalid Cloud SQL >>> name: <The connection name of your instance> >>> >>> On Sat, May 19, 2018 at 6:50 PM 'Kenworth (Google Cloud Platform)' via >>> Google App Engine <[email protected]> wrote: >>> >>>> @Lourdu >>>> >>>> You can try GitHub <https://github.com/>, Bitbucket >>>> <https://bitbucket.org/product>, or similar repository tools. >>>> Preferably, post publicly only a skeleton app that would reproduce the >>>> issue. >>>> >>>> You mentioned files are < 250 kb but how many files do you have on your >>>> application? For example in Linux you can issue the following command to >>>> count the files on a directory: >>>> >>>> ls directory | wc -l >>>> >>>> -- >>>> 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 [email protected]. >>>> To post to this group, send email to [email protected]. >>>> 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/f71cfa13-4b96-4cea-b2b5-9fa2b92352a7%40googlegroups.com >>>> <https://groups.google.com/d/msgid/google-appengine/f71cfa13-4b96-4cea-b2b5-9fa2b92352a7%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> 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 [email protected]. >>> To post to this group, send email to [email protected]. >>> 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/CALdDuQ5iDjwHVNfGTu54iwWp64An2smvA%3Dqy9v76FF2m1bbvdA%40mail.gmail.com >>> <https://groups.google.com/d/msgid/google-appengine/CALdDuQ5iDjwHVNfGTu54iwWp64An2smvA%3Dqy9v76FF2m1bbvdA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > 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 [email protected]. > To post to this group, send email to [email protected]. > 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/CALegnbHUnA4gTZ%2B9sV-khnDxsq0J3zpHNbWJ22LvGFiw8Mb_Mw%40mail.gmail.com > <https://groups.google.com/d/msgid/google-appengine/CALegnbHUnA4gTZ%2B9sV-khnDxsq0J3zpHNbWJ22LvGFiw8Mb_Mw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/CALdDuQ5GNqBhunyoSXzqCZoRqzcbC9SsoonTUdPy8AcH4xQPCQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
