Can you elaborate on the terraform automation for gmail?

When we first built our user account system, we had to create a google user and add it to relevant groups in admin console whenever we hired someone, before the automation could kick in.

We're tired of that so we're looking into using a terraform provider [1], so that we can declare new users and instantiate their resources with a simple PR.

[1]: https://registry.terraform.io/providers/hashicorp/googlework...

Sigh.

Same thing happened to me once. I called google support and they send me another phone.

Same here. It seems very unlikely they would not resend a phone lost in delivery. When it happened to me, they immediately ordered a replacement device.

If OP lurking here, How do you manage versioning terragrunt/terraform?

May be you can share your source here to benefit all.

Whenever this kind of things happens. It will make all the more difficult for startups to acquire users because this reiterates "Startups are either going to be acquired and killed or die prematurely".

This hurts, because Pebble always seemed to me like the "good" kind of startup that will live long.

Unfortunately they didn't grow responsibly.

I worked for a start-up that did a similar thing. We hired tons of people and the business was unsustainable. It was a push to get bought or go out of business. Lucky for us we got bought.

Can I use this for my SaaS?

I have successfully used an Android device as a cheep SMS gateway. An app installed on the device acted as the gateway and messages are triggered from the server via GCM push messages to the device.

Incoming messages to the device are intercepted by a receiver on the device and posted back to the server.