Add {cloud,glass,play}.google.com to the preloads.

Add {cloud,glass,play}.google.com to the preloads.

R=rsleevi@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=239005

[palmer, 2013-11-22 19:17:17]

Is it OK to set pins too, or should we just do HSTS? This is at lcamtuf's
request.

[lcamtuf1, 2013-11-22 19:19:03]

On 2013/11/22 19:17:17, Chromium Palmer wrote:
> Is it OK to set pins too, or should we just do HSTS?

I think there's no reason why it shouldn't be pinned.

[agl, 2013-11-22 19:30:09]

Have we gotten the ok for cloud.google.com? That's the only one that looks
possibly risky.

[lcamtuf1, 2013-11-22 20:22:59]

On 2013/11/22 19:30:09, agl wrote:
> Have we gotten the ok for cloud.google.com? That's the only one that looks
> possibly risky.

I don't think that any of the existing entries were directly reviewed by service
owners (cevans knows for sure), but we can sure reach out to them now if you
prefer (cloud.google.com is essentially the next-gen version of
appengine.google.com, which is on the list).

[Ryan Sleevi, 2013-11-25 06:29:43]

Rubberstamp LGTM so you can land through the CQ, but let's ping service owners
to be sure

[commit-bot: I haz the power, 2013-12-05 18:24:19]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/palmer@chromium.org/82703005/1

[commit-bot: I haz the power, 2013-12-05 18:48:37]

Retried try job too often on chromium_presubmit for step(s) presubmit
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=chromium_p...

[palmer, 2013-12-05 19:05:05]

Committed patchset #1 manually as r239005 (presubmit successful).