Chase

@joshua-rutherford I agree this is a bug and the logic is flawed, we should not be able to have two terraform resources connected to the same email and trading updates.

Could be a bug somewhere [here](https://github.com/DeviaVir/terraform-provider-gsuite/blob/master/gsuite/resource_user.go#L732-L741) though we do a bunch of boolean updates like that, so I wonder if it might be something extra we need to do in...

https://github.com/DeviaVir/terraform-provider-gsuite/commit/29f99d1f1f46ff93b30e76d5f791ae5e7321c098

Please give `v0.1.62` a try https://github.com/DeviaVir/terraform-provider-gsuite/releases/tag/v0.1.62

This terraform registry dying on random bs is really getting old..............

Done

You can use the forks I link in https://github.com/zaproxy/actions-common/pull/198 @alecor191, they contain the patches and don't lead to any rate limits. I'll try to keep it in sync, hopefully it...

Off-topic: it's ages ago, but iirc I published that to grab a new version to use in zenbot. If you look at the homepage on that NPM package you'll see...

ping @robinjmurphy

Yes, correct. I've added what I needed and opensourced it so others could extend it with whatever they used.