Problem
The vercel.TeamConfig resource cannot be used to create or manage team configuration because the required id input (the Vercel Team ID) is stripped by the Pulumi-Terraform bridge.
The upstream Terraform provider defines id as a required string input on vercel_team_config:
// https://github.com/vercel/terraform-provider-vercel/blob/main/vercel/resource_team_config.go
"id": schema.StringAttribute{
Description: "The ID of the existing Vercel Team.",
Required: true,
PlanModifiers: []planmodifier.String{
stringplanmodifier.UseNonNullStateForUnknown(),
stringplanmodifier.RequiresReplace(),
},
},
However, id is a reserved property in Pulumi's resource model (it represents the resource identity), so the bridge does not expose it in TeamConfigArgs. At runtime, the provider's Check function rejects the resource with:
error: vercel:index/teamConfig:TeamConfig resource 'my-team-config' has a problem:
Missing required property 'id': The ID of the existing Vercel Team.
This affects both new vercel.TeamConfig(...) and pulumi import.
Reproduction
import * as vercel from '@pulumiverse/vercel';
new vercel.TeamConfig('my-team-config', {
previewDeploymentSuffix: 'preview.example.com',
}, {
provider: myVercelProvider,
});
Setting team on the provider does not help — TeamConfig requires id explicitly in its own inputs.
Suggested fix
Remap id to teamId (or similar) in the bridge's SchemaInfo for this resource, so the Vercel Team ID can be passed through without colliding with Pulumi's reserved id field.
Environment
@pulumiverse/vercel: 4.6.1
- Pulumi CLI: latest
Problem
The
vercel.TeamConfigresource cannot be used to create or manage team configuration because the requiredidinput (the Vercel Team ID) is stripped by the Pulumi-Terraform bridge.The upstream Terraform provider defines
idas a required string input onvercel_team_config:However,
idis a reserved property in Pulumi's resource model (it represents the resource identity), so the bridge does not expose it inTeamConfigArgs. At runtime, the provider'sCheckfunction rejects the resource with:This affects both
new vercel.TeamConfig(...)andpulumi import.Reproduction
Setting
teamon the provider does not help —TeamConfigrequiresidexplicitly in its own inputs.Suggested fix
Remap
idtoteamId(or similar) in the bridge'sSchemaInfofor this resource, so the Vercel Team ID can be passed through without colliding with Pulumi's reservedidfield.Environment
@pulumiverse/vercel: 4.6.1