While I never spent a lot of time in GCP, it seemed like it was harder to understand GCP itself as a platform compared to AWS.
That is to say that Google APIs and services seem fine, but figuring out project management and infrastructure management feel incredibly weird. Not necessarily bad, but arcane and awkward where in AWS I can just hit the ground running.
Arguably, debatably, GCP might have the "more correct" model with resources scoped to projects and such, but it does make the learning curve harder.
> figuring out project management and infrastructure management feel incredibly weird
It's not just you, and the situation is worse than if they had no configuration management offering because, as Google is wont to do, they have several of them in various states of disrepair
- they cite terraform as their go-to deployment solution in damn near every blog post, but if you're trying to create something for (new users | deployment into _someone else's project_) the instructions start with "well, open a Terminal and ..."
- they now have some kind of "hosted terraform runner + state" whose name escapes me but is hiding somewhere in this list of a bazillion similarly named Cloud Somethings https://cloud.google.com/products?hl=en#section-14 ("Infrastructure Manager" is the one I was trying to think of https://news.ycombinator.com/item?id=37548639 and is, ha ha, not on that products page which is why I could not find it)
And speaking of, there is, of course, no way to enable project services via Deployment Manager, so pound sand if your Project was not already carefully configured in advance of Deployment Manager
That is to say that Google APIs and services seem fine, but figuring out project management and infrastructure management feel incredibly weird. Not necessarily bad, but arcane and awkward where in AWS I can just hit the ground running.
Arguably, debatably, GCP might have the "more correct" model with resources scoped to projects and such, but it does make the learning curve harder.