> Google Cloud Console dashboard…GCP is cannibalizing the Firebase developer environment. From an ops perspective, that makes sense. But axing the simplified cl

> Google Cloud Console dashboard…GCP is cannibalizing the Firebase developer environment. From an ops perspective, that makes sense. But axing the simplified cloud experience of Firebase removes much of its value > GCP favoritism… Why Firebase Hosting requires Cloud Function list authorization confounds me Someone gained promotion credits for these “migrations”. It’s turtles most of the way up. The bricklayers justify projects that are aligned with some director level’s visionary initiative to unify and consolidate GCP. If there was real vision, the fragmented and disjointed documentations and code packages should be normalized, but that is out of scope when you’re operating on promotion-cycle level timescales. On an orthogonal about cloud functions lost permissions, we wanted to list our cloud functions and since we used OAuth2 the most granular OAuth2 scope we requested involved the ability to write to GCP as a whole. Point being, there’s a pattern with GCP of forcing people to migrate to features that are half baked if not abandoned (again, promotion).