After the third occurrence of this i’d blame this on you, honestly.
After the third occurrence of this i’d blame this on you, honestly.
I'm sure they'd be happy to not have rely on having a Google Cloud account for integration with Google Cloud if possible.
Using GCP, AWS, or Azure is like volunteering to use your own money to rent heavy construction equipment to construct your own jail cell and excavate your own grave.
But hey, at least you get to avoid the capex on the heavy construction equipment, and it's always¹ available!
¹ except for when human error takes it offline for 14 hours straight
First time is a fluke, second time is a serious wake-up call, third time it's your fault.
Do you really want to reach the point where all your customers have an outage, you have to rush implementing something else (oidc or api keys) AND rush your customers to change your settings?
If you had actually read the post you would have understood there are ways to ditch GCP, but they are perceived as cumbersome.
The exaple is OpenID Connect. It works well with Azure (according to the post).
I'm sorry to say this, but the author is choosing something easy but unrealiable over something a bit more complicated but reliable.
It's really the author's fault. They are choosing their comfort over the service reliability (and keeping promises made to customers).
Heck they might even go with api keys. They could give explicit direction on the minimal amount of permissions the api key would need and they could ping the users each 3-4 months to rotate them.
But no, I guess we'll have another post at some point about the fourth (definitive?) account suspension.
That's nonsense. It requires a 7 step setup process that customers will mess up.