d024641022The 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.
10 lines
238 B
YAML
10 lines
238 B
YAML
name: mcp-access
|
|
runtime: nodejs
|
|
description: Infrastructure as Code for MCP access management
|
|
packages:
|
|
googleworkspace:
|
|
source: terraform-provider
|
|
version: 0.14.0
|
|
parameters:
|
|
- SamuZad/googleworkspace
|
|
- 0.11.1
|