non-slimey link:
https://nandovillalba.scribe.rip/why-i-think-gcp-is-better-t...and, as an AWS-er having to now support GCP, I violently and emphatically disagree with this:
> The experience of GCP on the other hand is more like collecting the car keys and driving off from the parking lot, with the option of dismantling and customising the car if you wish, but the default is a fully built functioning car with cohesive parts so you can quickly achieve your objectives, which is driving around, not assemble the car.
Oh, really? I invite the GCP newcomer to click on https://console.cloud.google.com/ create a new Project, and then run $(gcloud functions list) or, as the sibling comment pointed out, $(gcloud run jobs list) and watch it cheerfully tell you that you must turn on those services for each and every Project. And not just cloudfunctions.googleapis.com or run.googleapis.com, it's for damn near everything a sane person would want to use cloud computing for
I reiterate: you cannot turn on those APIs for your GCP "account," you must do it for each and every Project you create
Oh, you're the Super Admin for your Google account? Well, be sure you grant yourself the resourcemanager.projectCreator Role because as super admin you don't automatically have it
A reasonable person may retort that these are "secure by design" by opt-ing-in to surface area and permissions that one wishes to have, but as compared to "create AWS Account, start using ELB like it ain't no thing and I have AdministratorAccess granting me * permissions" -- let's not start talking about collecting car keys and driving off the lot