Deploy to app engine step hangs at the following:
INFO: Running command line: bazel-bin/cauliflowervest/server/main.deploy
11:58 AM Application: st-cauliflower; version: 1
11:58 AM Starting update of app: st-cauliflower, version: 1
11:58 AM Getting current resource limits.
I can't find any info about what's happening on this specific step.
In order to get to this step I had to manually add application:project-id, which wasn't in the wiki, but a page from a few years ago listed that as a bug. After getting stuck here I manually deployed the app.yaml file, and got errors saying the version field and application field are not used by gcloud and need to be removed. Commenting out both items allowed the app.yaml to deploy successfully, however the bazel based deploy fails when the application property is not in app.yaml:
appcfg.py: error: Expected -A app_id when application property in file app.yaml is not set.
ERROR: Non-zero return code '2' from command: Process exited with status 2
test-Mac:cauliflowervest tester$
From that is looks like the issue is in the bazel scripts, but I'm not sure what it is, or at what step.