This CL changes the GCE launcher to work with the new features of
camlistored: i.e. that it can automatically get a hostname in
camlistore.net, and that it can get an HTTPS certificate from Let's
Encrypt, for said hostname.
In order for the user to easily (without having to look at the logs)
know what their hostname is, camlistored stores it as the
"camlistore-hostname" key in the custom metadata of the GCE instance.
The deployer can then query for that key, to report the hostname on the
instance creation success page.
Change-Id: Iaaef2d51f34fa5e1e0ee90097919abab7ee72a12
The import path was added to the go file that included the package
documentation if one existed. Otherwise, I used what seemed to be the
primary file for the package.
Fixes#689
Change-Id: If51be0e86529fd6f179e80af6781e639f8550fd2
Previous oauth2 (code.google.com/p/goauth2/oauth) still used in:
third_party/github.com/tgulacsi/picago
pkg/importer/picasa
pkg/importer/foursquare
Final cleanup in a subsequent CL.
Change-Id: I805d81fcaa651e03a17823c78abe5040d51346c3
third_party/golang.org/x/net/context at 67f25490433376b5f7da086c0b9283fcdeca3a7b
third_party/golang.org/x/oauth2 at 5361962df4497a7fc777f5c3bd1b5c7ac36c604c
I only updated camdeploy, and did not remove code.google.com/p/goauth2
yet, because I do not want to get distracted by potential breakages, so
we can first get the gce deploy wizard in.
Change-Id: Ifa7987a044c741d3f00f49f47b31e3e07bdf973d
mpl