However, it would be fun if it had a UUID clash with a google service :)
I'd then assume once expression is evaluated the services end up busy looping / proxies throwing out internal errors and taking out capacity.
Still, you shouldn't be able to cause downtime to more then a few servers in the extremely unlikely case I am anywhere close.
PS: - I haven't used googles IAM so guessing after a few min of reading docs.
- you are incredibly unlikely to have triggered this at google's scale.
Wouldn't you rather call them directly on the hotline...?
That's a phone number from Bulgaria, and it looks like it should be part of the Vivacom GSM network, so I guess it's his personal mobile phone number or a scam.
Why not? It's not like you're gonna receive death threats exactly. I've had my personal phone number on my public website and in the footer of every outgoing email for 15+ years, never had any problems, spam or otherwise.
Had to do what it takes...
To save the company I work for and all of our customers data. Which all is in Google Cloud!
"IAM" is basically the name for a specific model of doing it.
Unless something really crazy happened, this user is unlikely to be correct. Accounts are supposed to be firewalled/sandboxed in a way that you can't contagion across to someone else's let alone systemwide.
It's possible (some sweeping script on a powerful connection that smashes just the right things or some exploit to break the sandboxing), just probably not likely - especially unintentionally.
But crazier things have happened https://books.google.com/books?id=rRp7DkTegMEC&newbks=0&prin...
Identity and Access Management (IAM)
besides google won't be exactly calling you because you made that comment here.
other commenters are right that you should not expose your personal number on internet regardless of it was you or not
Google more or less want people find their weaknesses so they can patch and secure them. A person accidentally triggering a global outage is not something that would cause that person to get lawyers on them. Especially not something that only affects his or hers GCP-project.
I had just plugged into a cable into the most important server in the organisation and I saw a bright flash and hear a bang.
All was well, it was just a coincidence, and a good reminder that sometimes shit happens and it's not us, it's just timing.
Relax.
