> Another service that would be very handy is a hosted etcd/Zookeeper service for service discovery, consensus, leader election, and distributed cron jobs.
> I have reported bugs/clarifications against AWS docs and got prompt feedback and even requests for clarification from AWS team members. This has never happened for my comments submitted against Google’s documentation.
I always submit "feedback" (for the last 2 years), but the lack of changes in the docs make them seem to disappear into a black hole, so I stopped doing so.
Would be great if the docs for GCP were on GitHub (like the K8s, and now AWS, documentation) so we can at least see that docs are being worked on and iterated, and share/validate common issues and suggest fixes.
Minor things like this also create a lot of developer confusion in large user orgs:
> The API libraries and tools are spread across several GitHub organisations including GoogleCloudPlatform, Google, and possibly others, which can make it a little difficult sometimes to track down the definition of something.
> It would be easier if I didn’t need to think about this API access
Thank you for the feedback. While I can't share specific details, we are always looking for ways to improve the documentation, bug reporting, and feedback process.
I also totally agree that these little things matter, even for small organizations. An incorrect or incomplete piece of documentation can cost someone hours or days, not to mention the emotional cost. Rest assured that we are working to make the experience better.
> ...keeping those metropolitan areas that have had the best job growth over the last decade, according to Bureau of Labor Statistics data. Metro areas that have actually lost jobs (Tucson; Birmingham, Ala.) and those that have grown more sluggishly are out of the running.
The cloudbuild service operates some other services on your behalf, and their relevant charges apply.
This most notably includes Cloud Storage (GCR is backed by Cloud Storage). If you use 'gcloud container builds submit' to kick off a build, Cloud Storage is used to get the source in as well.
I agree, the semantics required to define the build in GCCB seems really limiting, going to stick to Drone until this matures a bit. The plugin ability of Drone really outshines the current as well.
This is probably the best case of out-in-the-open open source developers of similar-but-different tools collaborating on a new standard and implementing them in record time that I have ever seen.
"Heck, even Canada now has a law that makes using Dropbox illegal if you are working with personal data (at least until Dropbox starts storing that data in Canada, or that’s what I was told). It’s called PEPIDA."
It's actually called PIPEDA, not PEPIDA.
Also, where is the source? I have done a good share of readings in this topic as part of my research in a Canadian university (< 4 months ago) and could not find the "illegal"-ness of such actions.
Currently, the act essentially outlines consent and putting the knowledge and power to update/remove private information with the users, and does not outline what services or actions are illegal.
It is important for people care about privacy, but it is not cool to post un-sourced opinions as facts, as people often mis-cite them as fact and propagate false info.
