3 ms·

As someone that works solely in a GCP environment for work, I couldn't agree more. GCP products do "just work", but if I had to nitpick, it's that some of their

• kapilvt 6y ago
  As someone who just dealt with the questionable state of the gcp docs, I couldn't disagree more, afaics there's really no qa on this stuff. to wit, the official docs for turning on storage bucket uniform access are a missing a parameter, that we only found after turning on http tracing on gsutil. The docs themselves are very spread out, and frequently have errors or inconsistencies (ie use beta v1 of this, v1 of that, and alpha v1 for different resources in the same service). Unlike aws or azure, none of the actual api specs (json data) or even the official cli implementation is in a public repo. For python alone, googlers maintain like 4 different implementations of the api, 'nough said.
  • hodgesrm 6y ago
    I've also had some bad encounters with the GCP docs, particularly around object storage. That was a while ago and may have been fixed. Early on they were not consistent with the actual APIs and poorly organized to boot. It was complicated by the fact that the APIs seem to have shifted. Amazon overall has done an excellent job on documentation. It's made easier by the fact that they rarely change API behavior once it's deployed.