terraform-provider-vercel

Summary make writable for project deployment checks support deployment and filtered Turborepo task selections infer the API-only and job fields validate source-specific field combinations and preserve selections on import/read add client/resource coverage and generated documentation Validation regenerated provider docs local tests not run per workspace policy; CI will run the unit and acceptance suites API cleanup: https://github.com/vercel/api/pull/99726

Add to create teams within an existing organisation, where billing is already configured. It requires an and an explicit or billing plan, and returns a team ID that works with and existing project resources. It manages the team's name and slug and supports importing existing child teams. The example references the team's name and slug from so both resources stay consistent during renames. Unset settings on newly created teams now remain null in , avoiding repeated changes on subsequent plans. Destroy deletes the team rather than detaching it. The API currently refuses self-service deletion of Enterprise child teams; those failures leave the resource in state. The example uses , and changing the organisation or billing plan requires replacement. Closes ORC-5407.

Summary Adds , which lets a consumer project in the same team read the flags of a source project (Vercel Flags project connections). API Create: with Read: (no single-get endpoint, so read lists and filters by ) Delete: All fields force replacement; import via . Notes The endpoints are currently and gated per team ( when connections aren't enabled). Keeping this as a draft until the API is public. The source project must have Flags enabled; the acceptance test creates a flag definition first, like the SDK key test. needs a testing team with connections enabled. Testing [x] Client unit tests () [ ] Acceptance test (not run, needs team with connections enabled) 🤖 Generated with Claude Code