modelcontextprotocol/access
Watch
1
0
Fork
You've already forked access
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix: resolve GWS user creation timeout in Deploy workflow

Browse source 
The hashicorp/googleworkspace provider has a known eventual-consistency
bug (issue #387): after creating a user, it polls for 4 consecutive
identical API etags before marking the resource created. Google's API
frequently flip-flops etags, so the check never passes and the 300s
default timeout trips — even though the user was actually created.

This caused cliff@ creation to timeout, leaving the user in GWS but not
in Pulumi state; subsequent runs fail with 409 Entity already exists.

Two changes:
- Mark cliff as existingGWSUser so Pulumi stops trying to create him
  (matches the pattern used for other stranded users).
- Switch to the SamuZad/googleworkspace fork (v0.11.1), which lowers
  numConsistent from 4 to 2, preventing the timeout for future user
  creations. The upstream provider has been unmaintained for 2+ years.
This commit is contained in:
David Soria Parra 2026-03-09 10:24:14 +00:00
commit d024641022
No known key found for this signature in database
1 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

3
Pulumi.yaml
View file

@ -6,4 +6,5 @@ packages:
source: terraform-provider
version: 0.14.0
parameters:
- hashicorp/googleworkspace
- SamuZad/googleworkspace
- 0.11.1