search

viur-framework / viur-cli

Command-line interface for managing and developing ViUR
MIT License
4 stars 6 forks source link

bug: Run `viur cloud setup gcloud` in an empty project folder generates confusing results #128

Open phorward opened 5 months ago

phorward commented 5 months ago

Hello!

I'm currently experimenting with Google Cloud Shell and tried to run a viur cloud setup gcloud command in my home folder, with a fake project.json and no deploy folder.

$ viur cloud setup gcloud
Enter PROJECT_ID: xxx-viur3
Check if user is authorized with gcloud....
Operation "operations/acat.p2-799407658776-5713ecae-5dde-4a55-b286-26f9ab92b842" finished successfully.
Operation "operations/acf.p2-799407658776-fbf62221-ce5e-4f8b-a10b-4e2555e5b9b5" finished successfully.
Operation "operations/acat.p2-799407658776-3f617a3e-55aa-4092-97c0-23d40dba8aaf" finished successfully.
Operation "operations/acf.p2-799407658776-1bf01b22-97a1-4745-b735-d1237862a742" finished successfully.
Operation "operations/acf.p2-799407658776-6756081d-adac-4c44-a0db-973e9554a6ad" finished successfully.
Operation "operations/acf.p2-799407658776-8da2776e-f8f0-4194-94f0-86aa6d6e6acf" finished successfully.
Operation "operations/acat.p2-799407658776-e34a8bae-8f06-417c-9eb9-542858c30dce" finished successfully.
/bin/sh: line 1: cd: deploy: No such file or directory
Error executing command: Command 'cd deploy && gcloud app deploy -q --project=xxx-viur3 cron.yaml' returned non-zero exit status 1.
/bin/sh: line 1: cd: deploy: No such file or directory
Error executing command: Command 'cd deploy && gcloud app deploy -q --project=xxx-viur3 queue.yaml' returned non-zero exit status 1.
/bin/sh: line 1: cd: deploy: No such file or directory
Error executing command: Command 'cd deploy && gcloud app deploy -q --project=xxx-viur3 index.yaml' returned non-zero exit status 1.
Check if app engine default credentials are set...
INFO: All done!
You should now be able to run your project locally with
   viur run 
At the first run, it might happen that some functions are
causing error 500 because indexes are not immediately
served. Therefore, maybe wait a few minutes.
Have a nice day.

This result is confusing. Generally, the workflow should in this case be something like viur init to initialize a new, empty base-project. viur cloud setup gcloud should fail immediatelly when there is no deploy folder, with a hint that viur init should be executed first.

phorward commented 5 months ago

viur init is in a separate issue #129

phorward commented 1 month ago

viur init is in a separate issue #129

129 was replaced by #165, viur cloud setup gcloud should still be fixed either.