3 ms·
That is good to know, however my first reaction when reading this is we shouldn't be using G Suite for admin@corp or bob@corp, but rather if I am going to be se
by nkw 10y ago
That is good to know, however my first reaction when reading this is we shouldn't be using G Suite for admin@corp or bob@corp, but rather if I am going to be seriously dependent on Google Cloud I should perhaps move e-mail for said @corp to Office365 (or whomever else actually does e-mail these days). I don't know what the solution/answer is here, but it worries me that actions (yes even bad spam-y TOS violating actions) that someone takes using our company's google accounts can ripple across the Google ecosystem and screw important parts of our company's infrastructure.
- jpatokal 10y agoYMMV (and this is my personal view, not necessarily Google's), but in general you want to have resources associated with active owners. Otherwise when Bob leaves, and his zombie solo project which you no longer have any control over gets pwned, you're going to have an even bigger problem.
- naasking 10y agoNo one's denying that orphaned projects are a problem, but if deactivating an e-mail has downstream effects like this, you'd expect a warning or something before permitting account deactivation.
- stickfigure 10y agoHow would you expect to receive this warning?
- gselva 10y agoIn my case, where the email was hosted in Google apps, it would have been helpful if Google apps had checked with GCE before allowing email deletion. After all, this is one of the situations where being within Google Eco-system should have been a good thing.
- naasking 10y agoAgreed. Or force the user to have two registered e-mails in a GCE account at all times, unless they're explicitly deleting it. Doing things implicitly with no warning is simply terrible UX.