ah ok. I'm glad to hear mvn/gradle plugins aren't going anywhere. seamless integration with the ecosystem's popular build system is something I've always liked about the GAE approach.
as for goapp vs gcloud, currently I'm concerned about reproducible build. goapp is a single tool with its own go tool chain, I don't have to worry about "which version of go to use for what". this causes issue to be sure, 3rd party packages using context is the big sore point. the gcloud way, requires you to install gcloud, and then your own go toolchain, which currently you can't use anything higher than 1.6. This gives me pause. Since there is an external go toolchain that I have to install and yet have to make sure I don't upgrade it to a version that causes issues. Right now it's bad, when GAE 1.8 comes out we'll have a brief "all is right in the world because it's 1.8 everywhere". But when GAE finally hits 1.8. what happens when go 1.9 comes out? Am I still going to be in a situation where I have to install 1.8 for gcloud until such time gcloud moves to 1.9? and then there is also the issue that we use go outside of GAE. Those we aggressively upgrade to the latest go release. Using gcloud means we'll more likely than not, having to have 2 sets of go toolchain installed. where as goapp, I just download the latest one, it's a sandbox that I won't need to touch for any non-GAE stuff. Thanks, On Tue, Apr 25, 2017 at 1:51 PM, 'Justin Beckwith' via Google App Engine < google-appengine@googlegroups.com> wrote: > Great feedback! To a few points: > > I've been very happy with the java tool chain where it integrate perfectly >> into existing JVM build tools via plugins for mvn and gradle. I'm not sure >> what gcloud tool brings to the table. > > > I should have mentioned this - those aren't going anywhere. All of the > Maven/Gradle/IntelliJ/Eclipse/VS stuff will continue to be distributed on > it's own. > > I prefer the goapp approach > > > Interesting. Is this just about the single tool philosophy, or is there a > specific thing goapp does better than gcloud? > > Thanks! > > > > On Tue, Apr 25, 2017 at 10:41 AM, Wilson MacGyver <wmacgy...@gmail.com> > wrote: > >> I'm concerned about the one tool fits all approach. It'd be one thing of >> the "single tool" gcloud is just a thin wrapper to automatically download >> and configure each component as needed. What I'm afraid of is unnecessary >> dependency. Ie, the latest go GAE sdk is being hold up by the latest >> gccloud release. >> >> There are some of us that only use GAE, and has no interest using the >> rest GC service such as GKE, GCE, etc. I've been very happy with the java >> tool chain where it integrate perfectly into existing JVM build tools via >> plugins for mvn and gradle. I'm not sure what gcloud tool brings to the >> table. >> >> If there are very few of us that only uses GAE. or that google doesn't >> really want us to only use GAE, I understand. But forcing me to use gcloud >> instead of say a gradle/mvn plugin feels like just more moving parts to me. >> >> with go, I'm a bit more desperate. I prefer the goapp approach, but given >> that go version on GAE is so behind that if gocloud is the 'only way' to >> make 1.8 happen faster, then I'll learn to deal with it. >> >> >> for me, up till now Google cloud's strength has been a much more unix >> like experience. You use gsutil if you want to deal with cloud storage, >> goapp for GAE-go, etc etc. I'm a bit surprised to see google moving toward >> the aws where you use aws-cli for everything. >> >> Just my 2 cents >> >> >> On Tue, Apr 25, 2017 at 12:45 PM, 'Justin Beckwith' via Google App Engine >> <google-appengine@googlegroups.com> wrote: >> >>> Hey folks, >>> Apologies for the confusion. Here's what's happening. >>> >>> *We are trying to move towards a single Cloud SDK install.* At the >>> same time, we're trying not to break the existing App Engine SDK >>> downloads. We are headed towards a future (not far away) where everything >>> gets wrapped up into https://cloud.google.com/sdk/. Instead of having >>> separate SDKs for Go/Python/Java/PHP >>> <https://goto.google.com/Python/Java/PHP>, we want one toolchain. >>> >>> *We are moving towards tooling consistency.* The goal is to make >>> `gcloud app deploy` work for each language supported by App Engine. With >>> the exception of Java, we're mostly there. You should be able to use >>> `gcloud app deploy` and `dev_appserver.py .` instead of `goapp update ` or >>> `goapp serve`. >>> >>> I'm interested in getting some feedback on this approach. Do you feel >>> like `gcloud app deploy` and `dev_appserver.py .` are enough? Or are there >>> other reasons you want to keep using `goapp`? >>> >>> Is this just a matter of unclear documentation? >>> >>> Thanks! >>> >>> >>> On Tue, Apr 25, 2017 at 1:21 AM, Michael Amie <michael.a...@gmail.com> >>> wrote: >>> >>>> Tim, >>>> >>>> You are not insane. I have noticed this as well w/ respect to the >>>> missing executable bit set on at least one of the goapps (and if I recall >>>> correctly, when I looked into this a month or so ago), several other >>>> scripts / binaries weren't set to executable as well, post-installation. >>>> >>>> As you mention, I got the impression the stand-along "go SDK" was being >>>> phased out / deprecated and this was getting rolled into the cloud SDK as a >>>> module / component for it. >>>> >>>> It seems like they didn't test the new installer or something before >>>> rolling it out, and based on the combo of 1. The broken install and 2. The >>>> doublespeak of the documentation, I'd wager there is some sort of >>>> miscommunication or something between teams / departments going on right >>>> now about what's going on during this transition. >>>> >>>> I'd love to see Google actually get all their documentation updated / >>>> synced with the One True New Way and it would be good if they tried running >>>> this new installer on a few Mac OS versions to see if it actually works. >>>> >>>> Thanks, >>>> Michael >>>> >>>> On Saturday, April 8, 2017 at 8:57:29 AM UTC-7, Tim Becker wrote: >>>>> >>>>> Sorry if I'm missing something obvious, but it seems that the >>>>> documenation is very unclear about this and was just recently changed with >>>>> no clear migration instructions: >>>>> >>>>> - since recently (~ last week sometime) the prefered way to >>>>> install Golang support seems to be via the "Google Cloud SDK" (vs the >>>>> "original App Engine SDK for Go") >>>>> - previously, the `goapp` tool was a central part of my workflow >>>>> in order to deal with the dependency on the completely outdated 1.6 >>>>> version >>>>> of Go required by appengine >>>>> - using gcloud and installing go support via `gcloud components >>>>> install app-engine-go` gets me two `goapp`s: >>>>> - ./google-cloud-sdk/platform/google_appengine/goapp >>>>> - ./google-cloud-sdk/platform/google_appengine/goroot/bin/goapp >>>>> - the first of which is a python script with no executable bit >>>>> set, and neither of which are in the PATH set up by the install.sh >>>>> script >>>>> - running, eg. `./google-cloud-sdk/platform/g >>>>> oogle_appengine/goroot/bin/goapp test` results in the following >>>>> error: >>>>> - `go: cannot find GOROOT directory: >>>>> /private/var/folders/bs/nn10qt5j32g25qwgd77wkcyh00d7l1/T/app >>>>> engine/go_appengine/goroot >>>>> >>>>> Now there are `gopath` and `goroot` dirs in the >>>>> `plattform/google_appengine` directory and I'm tempted to set the >>>>> corresponding environment variables to point to those directories, because >>>>> at least `goroot` seems to have all the necessary appengine dependencies >>>>> install in it. But this leaves me wondering, where my app should reside. >>>>> And dealing with appengine/gcloud/whatever it's called today in this >>>>> manner >>>>> feels just like "trying out random stuff" >>>>> >>>>> The README contains completely outdated info from 2008. And the online >>>>> docs only seems to focus on using the "classic" SDK (e.g. >>>>> https://cloud.google.com/appengine/docs/standard/go/to >>>>> ols/localunittesting/) >>>>> >>>>> Is there any obvious documenation that I'm missing? Am I the only >>>>> person encountering these problems? >>>>> >>>>> >>>>> (btw. I'm using OSX) >>>>> >>>> -- >>>> 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/ms >>>> gid/google-appengine/abb82812-08a4-4bec-af3c-4bf7bac25e58%40 >>>> googlegroups.com >>>> <https://groups.google.com/d/msgid/google-appengine/abb82812-08a4-4bec-af3c-4bf7bac25e58%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> >>> Justin Beckwith | Google Cloud Platform | @justinbeckwith >>> <http://twitter.com/JustinBeckwith> | http://jbeckwith.com >>> >>> -- >>> 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/ms >>> gid/google-appengine/CADd%3D1Q02VhgPRjUxAa_doUhL4qxeRxwF12Q1 >>> sKZffOAt5g4DhQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/google-appengine/CADd%3D1Q02VhgPRjUxAa_doUhL4qxeRxwF12Q1sKZffOAt5g4DhQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Omnem crede diem tibi diluxisse supremum. >> >> -- >> 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/ms >> gid/google-appengine/CAM0dQnn0DK0BKrNFcx2Z_YTjraULf6DeSCtLv1 >> i%2B5Bn6qWmaBQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/google-appengine/CAM0dQnn0DK0BKrNFcx2Z_YTjraULf6DeSCtLv1i%2B5Bn6qWmaBQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > > Justin Beckwith | Google Cloud Platform | @justinbeckwith > <http://twitter.com/JustinBeckwith> | http://jbeckwith.com > > -- > 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/CADd%3D1Q1GaOhVvGxEt-BPiGu% > 2Brkgppi5WyOFMMyFQAExQhX%3D8Ww%40mail.gmail.com > <https://groups.google.com/d/msgid/google-appengine/CADd%3D1Q1GaOhVvGxEt-BPiGu%2Brkgppi5WyOFMMyFQAExQhX%3D8Ww%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Omnem crede diem tibi diluxisse supremum. -- 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/CAM0dQn%3DgceFEevYiJY3d8YrbqVTnCNL-%3DPCrzPFv8pYyYnEc3Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
