Description

The current implementation of vercel_project_environment_variable and vercel_project_environment_variables resources restricts the target field to only accept production, preview, or development. However, Vercel has recently released Custom Environments feature which allows for user-defined environment names.

Current Behavior

The provider enforces a strict validation on the target field, only allowing:

• production
• preview
• development

Expected Behavior

The target field should accept any string value to support Vercel's Custom Environments feature, while maintaining backwards compatibility with the existing environment names.

Example Usage

resource "vercel_project_environment_variable" "example" {
  project_id = vercel_project.example.id
  key        = "API_KEY"
  value      = "secret-value"
  target     = ["staging"]  # Currently not possible
}

Documentation for Custom Environments: https://vercel.com/docs/deployments/custom-environments
Vercel CLI using target for environments: https://vercel.com/docs/cli/deploy#target