Closed dsiebel closed 3 years ago
UPDATE: The segfault occurs after some sort of timeout, trying to authenticate. I switched our setup from using Workload Identity back to using the JSON key of the Service Account directly.
Still, there seems to be an issue in the provider when a timeout occurs in the auth process, causing the SIGSEGV. I adjusted the title accordingly.
Did some digging through the code, it looks like the combination empty Credentials
(should be empty because Workload Identity doesn't require us to set GOOGLE_APPLICATION_CREDENTIALS
or similar)
https://github.com/DeviaVir/terraform-provider-gsuite/blob/v0.1.60/gsuite/config.go#L62
and ImpersonatedUserEmail
being set
https://github.com/DeviaVir/terraform-provider-gsuite/blob/v0.1.60/gsuite/config.go#L96
leaves client
without any value, which then is accessed to assign client.Transport
https://github.com/DeviaVir/terraform-provider-gsuite/blob/v0.1.60/gsuite/config.go#L125
Looks like this issue was fixed in https://github.com/DeviaVir/terraform-provider-gsuite/pull/175 and released as https://github.com/DeviaVir/terraform-provider-gsuite/releases/tag/v0.1.61
Sadly v0.1.61 is not yet available via the public Terraform registry. Any ETA when this will be available?
Strange, it's complaining about missing release asset for ["terraform-provider-gsuite_0.1.61_SHA256SUMS"]
which is available in the tagged release
Any chance you can fix it? 😜
Apparently pressing Resync
a few times a day fixes it. https://registry.terraform.io/providers/DeviaVir/gsuite/latest
Thank you very much, will try it asap!
Our terraform state started segfaulting on every plan after the recent upgrade to the newest terraform version and the newest version of the gsuite provider.
Background: We are using the GSuite provider in a rather large terraform state.
plan
andapply
are executed using Atlantis running on Google Kubernetes Engine authenticating via Workload Identity. I recently updated the entire stackSince the upgrade all plans fail with a SIGSEGV in the GSuite provider. I encountered multiple segmentation violations in the past using this provider and was always able to work around them, this time I have no clue where to start.
The gsuite provider was used with
~> 0.1.54
version constraint so I assume that we were already using 0.1.60 shortly after it was released.Error output: