SamuZad

The core of the issue is: when creating the chart, the secret is created as a pre-hook resource, and is therefore not part of the helm chart proper. Therefore if...

Implemented this for my fork: https://github.com/SamuZad/terraform-provider-googleworkspace/commit/437bba98faed8b667fb8f3e79b1a7159dea76468 https://registry.terraform.io/providers/SamuZad/googleworkspace/latest

Update on this: this introduced a new (and imo quite annoying problem) - if one commented out the aliases attribute completely but the previous iteration had aliases, the plan would...

I finally had time to implement this for my fork 😅 https://registry.terraform.io/providers/SamuZad/googleworkspace/latest/docs/resources/user#nestedblock--on_delete_data_transfer https://github.com/SamuZad/terraform-provider-googleworkspace/commit/834b20a9187ca8f4f1721c79c39cdf5f201f9361

This is rather annoying, although it seems like it's caused by a sneaky API change.. I got paranoid about people archiving groups 😓

This is an issue relating to the google APIs eventual consistency, and how the provider handles the checks for said eventual consistency I significantly improved this in my fork: https://registry.terraform.io/providers/SamuZad/googleworkspace/latest/docs...

This is really cool! As it appears that this provider is not being maintained, would you mind if I adopted this into my fork? Reference issue: https://github.com/hashicorp/terraform-provider-googleworkspace/issues/464

We don't. Why do you ask?

This issue now seems resolved. On our end, at least, we no longer run into `Error: googleapi: Error 409: Member already exists., duplicate` Seems like the underlying API issue is...

So, there are 2 issues here: 1. The terraform user genuinely does not have permissions to do the operation (I will disregard that part for now) 2. The terraform user...