Thanks for the feedback. Regarding the switch to different projects, one can use the global flag *--project=my_project_id* <https://cloud.google.com/sdk/gcloud/reference/> for a given command to be performed with a specific context. Alternatively, one could use *gcloud config set project my_project_id <https://cloud.google.com/sdk/gcloud/reference/config/set>* to achieve a longer term effect. This will remain in effect until changed.
The default behavior to promote a new deployment can be changed per deployment using the *--no-promote <https://cloud.google.com/sdk/gcloud/reference/app/deploy>* flag. If you wish deployments *not* to be promoted by default, you can use *gcloud config set app/promote_by_default false <https://cloud.google.com/sdk/gcloud/reference/app/deploy>*. This will remain the new default behavior unless changed or using the *--promote* flag when deploying. Depending on the needs of your company, you may want to consider the App Engine Admin API <https://cloud.google.com/appengine/docs/admin-api/getting-started/>. These APIs allow you to create applications, create/list/delete service versions, etc. programmatically. With these operations, you could make your own custom user interface for managing your projects, applications and services. On Wednesday, December 21, 2016 at 3:36:57 PM UTC-5, Joshua Smith wrote: > > Having used both, the GUI is much better in two cases: > > 1. When you have a lot of projects, it’s nice to have the GUI to just > click and update, vs having to root around finding the right script to run. > > 2. I could train a non-programmer to push an update to a web app using the > GUI. Not so using the command line. > > Also, the whole setup for the command line is really focused on the idea > that you’ll have only one project, which is pretty silly. So you end up > having to write simple scripts as wrappers around the command line stuff, > just to pass project names. > > And one other issue with the command line that was really just a violation > of the principle of least surprise: deploying should NOT route all traffic > to the version you just pushed. That’s insane. Whoever thought that was a > good default clearly has no experience developing real applications. Not a > big deal to work around because I have to write the aforementioned wrapper > scripts anyway, but… seriously? > > -Joshua > > On Dec 21, 2016, at 2:39 PM, 'Nicholas (Google Cloud Support)' via Google > App Engine <google-appengine@googlegroups.com> wrote: > > I am not aware of any plans to create a GUI for the Cloud SDK. > > - Are there particular features of the launcher that are unavailable > or difficult to use with gcloud command line tool? > - Are there any particular pain points to the *gcloud* command line > tool? > > > On Wednesday, December 21, 2016 at 1:31:10 PM UTC-5, George Bittmann wrote: >> >> The App Engine Launcher was largely how I was able to sell my team on >> using App Engine. >> >> Nicholas do you know if there are plans to create a GUI product for App >> Engine using the new Cloud SDK? >> >> Knowing one way or the other will be helpful. >> >> >> >> >> On Monday, December 19, 2016 at 4:54:41 PM UTC-5, Nicholas (Google Cloud >> Support) wrote: >>> >>> Thank you for voicing your concerns. >>> >>> I can confirm that we are strongly moving towards having App Engine a >>> component of the Cloud SDK but there are no public plans to deprecate the >>> App Engine SDKs. >>> >>> If you wish to have multiple services running using dev_appserver.py, >>> you can do so by by running multiple instances of them. As stated in the >>> Local Development Server Options >>> <https://cloud.google.com/appengine/docs/python/tools/local-devserver-command> >>> under the *--port* option: >>> >>>> If multiple servers are launched, they will be assigned subsequent >>>> ports (e.g. 8081, 8082, etc) >>> >>> >>> We are aware of user base that prefers the App Engine Launcher. Apart >>> from that, should there be other features that you would like to see >>> implemented in the Cloud SDK, please feel free to file a feature request on >>> the Cloud Platform public issue tracker >>> <https://code.google.com/p/google-cloud-sdk/issues/list>. We welcome >>> the feedback. >>> >>> On Thursday, December 8, 2016 at 2:48:35 PM UTC-5, Hannes Rydén wrote: >>>> >>>> I've been developing sites for App Engine Python for years and have >>>> always loved the Google App Engine Launcher client for Windows. It makes >>>> developing and publishing websites a breeze, compared to most other web >>>> server software. >>>> >>>> Now I wanted to install the latest version, clicked the download button >>>> as usual but were then lead to install the Cloud SDK client instead. So I >>>> did. But gone was the simple graphical interface, and I was met with a >>>> confusing terminal interface instead, which seemed much more limited in >>>> functionality (can I even have multiple sites running at the same time on >>>> different ports?). I can't even find how to start the program again after >>>> I >>>> shut it down. >>>> >>>> I finally found the old client download, which was hard to find without >>>> reading forums. Why would you recommend users to use a clearly inferior >>>> product in terms of usability? I think that will deter many new users from >>>> developing on App Engine. >>>> >>>> I think it would be much better if you make the old Launcher the >>>> recommended tool for App Engine instead, and provide the Cloud SDK an >>>> alternative. I really love App Engine, so that's why I'm sad to see when >>>> some new changes seem to make it worse (which is usually not the case, as >>>> you've been making some great changes over the years). >>>> >>> > -- > 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/9e5505ef-bcf7-4d64-870f-9b323793ca47%40googlegroups.com > > <https://groups.google.com/d/msgid/google-appengine/9e5505ef-bcf7-4d64-870f-9b323793ca47%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 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/95c19d8b-c17d-4af2-866a-21f6af9934e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
