### Deploying a single file with vercel_file and vercel_deployment

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/file.md

This example demonstrates how to use the vercel_file data source to get metadata for a file and then use that metadata with the vercel_deployment resource to deploy the file. Ensure the file path is relative to your Terraform configuration.

```terraform
data "vercel_file" "example" {
  path = "index.html"
}

data "vercel_project" "example" {
  name = "my-project"
}

resource "vercel_deployment" "example" {
  project_id = data.vercel_project.example.id
  files      = data.vercel_file.example.file
}
```

--------------------------------

### Example Usage of vercel_blob_project_connections

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/blob_project_connections.md

This example demonstrates how to configure a Blob store, a Vercel project, establish a connection between them using `vercel_blob_project_connection`, and then use the `vercel_blob_project_connections` data source to read these connections.

```terraform
resource "vercel_blob_store" "example" {
  name = "example-blob-store"
}

resource "vercel_project" "example" {
  name = "example-blob-project"
}

resource "vercel_blob_project_connection" "example" {
  blob_store_id = vercel_blob_store.example.id
  project_id    = vercel_project.example.id
}

data "vercel_blob_project_connections" "example" {
  store_id = vercel_blob_store.example.id
}
```

--------------------------------

### Example Usage of vercel_prebuilt_project

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/prebuilt_project.md

This example demonstrates how to use the `vercel_prebuilt_project` data source to reference a pre-built UI project and then use its output to create a Vercel deployment. It assumes the UI project is in a separate directory and has been built using `vercel build`.

```terraform
data "vercel_project" "example" {
  name = "my-awesome-project"
}

data "vercel_prebuilt_project" "example" {
  path = "../ui"
}

resource "vercel_deployment" "example" {
  project_id  = data.vercel_project.example.id
  files       = data.vercel_prebuilt_project.example.output
  path_prefix = data.vercel_prebuilt_project.example.path
}
```

--------------------------------

### Example Usage of vercel_microfrontend_group and vercel_microfrontend_group_membership

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/microfrontend_group.md

This example demonstrates how to create a Microfrontend Group and assign a project to it. It requires data sources to fetch project IDs.

```terraform
data "vercel_project" "parent_mfe_project" {
  name = "my parent project"
}

data "vercel_project" "child_mfe_project" {
  name = "my child project"
}

resource "vercel_microfrontend_group" "example_mfe_group" {
  name = "my mfe"
  default_app = {
    project_id = data.vercel_project.parent_mfe_project.id
  }
}

resource "vercel_microfrontend_group_membership" "child_mfe_project_mfe_membership" {
  project_id             = vercel_project.child_mfe_project.id
  microfrontend_group_id = vercel_microfrontend_group.example_mfe_group.id
}
```

--------------------------------

### Example Usage of vercel_project_directory and vercel_deployment

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/project_directory.md

This example demonstrates how to use the vercel_project_directory data source to gather file metadata from a local directory (e.g., '../ui') and then use that metadata along with project information to create a vercel_deployment resource. Ensure the path is relative to your Terraform files.

```terraform
data "vercel_project_directory" "example" {
  path = "../ui"
}

data "vercel_project" "example" {
  name = "my-awesome-project"
}

resource "vercel_deployment" "example" {
  project_id  = data.vercel_project.example.id
  files       = data.vercel_project_directory.example.files
  path_prefix = data.vercel_project_directory.example.path
}
```

--------------------------------

### Create a Vercel Project and a Project Route

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/project_route.md

This example demonstrates how to create a Vercel project and then define a project route for it. The route is configured to redirect legacy documentation paths to new guide paths with a 308 status code.

```terraform
resource "vercel_project" "example" {
	name = "example-project"
}

resource "vercel_project_route" "example" {
	project_id = vercel_project.example.id
	name       = "redirect-legacy-docs"
	position = {
		placement = "start"
	}
	route = {
		src    = "/docs/:path*"
		dest   = "/guides/:path*"
		status = 308
	}
}
```

--------------------------------

### Example Usage of vercel_bulk_redirects Data Source

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/bulk_redirects.md

This example shows how to use the vercel_bulk_redirects data source to retrieve bulk redirects for a project. Ensure the vercel_project resource is defined first.

```terraform
resource "vercel_project" "example" {
  name = "example-project"
}

data "vercel_bulk_redirects" "example" {
  project_id = vercel_project.example.id
}
```

--------------------------------

### Create a Vercel Project and Rolling Release

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/project_rolling_release.md

Example of creating a Vercel project and then configuring its rolling release with manual approval and defined stages.

```terraform
resource "vercel_project" "example" {
	name = "example-project"
	skew_protection = "12 hours"
}

resource "vercel_project_rolling_release" "example" {
	project_id = vercel_project.example.id
	advancement_type = "manual-approval"
	stages = [
		{
			target_percentage = 20
		},
		{
			target_percentage = 50
		}
	]
}
```

--------------------------------

### Example Usage

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/microfrontend_group_membership.md

Use this data source to retrieve information about an existing Microfrontend Group Membership. Ensure you have the project ID and microfrontend group ID.

```terraform
data "vercel_microfrontend_group_membership" "example" {
  project_id             = "prj_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
  microfrontend_group_id = "mfe_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
```

--------------------------------

### Example Usage of vercel_blob_object Data Source

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/blob_object.md

This example demonstrates how to use the vercel_blob_object data source to retrieve metadata for a Blob object. It first creates a blob store and then uploads an object, followed by fetching its metadata.

```terraform
resource "vercel_blob_store" "example" {
  name = "example-blob-store"
}

resource "vercel_blob_object" "example" {
  store_id              = vercel_blob_store.example.id
  pathname              = "branding/logo.svg"
  source                = "${path.module}/files/logo.svg"
  content_type          = "image/svg+xml"
  cache_control_max_age = 86400
}

data "vercel_blob_object" "example" {
  store_id = vercel_blob_store.example.id
  pathname = vercel_blob_object.example.pathname
}
```

--------------------------------

### Example Usage of vercel_access_group_project Data Source

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/access_group_project.md

This example demonstrates how to use the vercel_access_group_project data source to fetch information about an existing access group's project assignment. It first retrieves a project's ID using the vercel_project data source and then uses that ID along with a predefined access group ID to configure the vercel_access_group_project data source.

```terraform
data "vercel_project" "example" {
  name = "my-existing-project"
}

data "vercel_access_group_project" "example" {
  access_group_id = "ag_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
  project_id      = vercel_project.example.id
}
```

--------------------------------

### Example Usage of vercel_team_config

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/team_config.md

Use this resource to manage the configuration of an existing Vercel Team. Ensure the `vercel_file` data source is used to provide the avatar.

```terraform
data "vercel_file" "example" {
  path = "example/avatar.png"
}

resource "vercel_team_config" "example" {
  id                                    = "team_xxxxxxxxxxxxxxxxxxxxxxxx"
  avatar                                = data.vercel_file.example.file
  name                                  = "Vercel terraform example"
  slug                                  = "vercel-terraform-example"
  description                           = "Vercel Terraform Example"
  sensitive_environment_variable_policy = "off"
  remote_caching = {
    enabled = true
  }
  enable_preview_feedback         = "off"
  enable_production_feedback      = "off"
  hide_ip_addresses               = true
  hide_ip_addresses_in_log_drains = true
}
```

--------------------------------

### Create a Vercel Project Domain

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/project_domain.md

Example of creating a simple domain associated with a project. This domain will be automatically applied to production deployments.

```terraform
resource "vercel_project" "example" {
  name = "example-project"
}

# A simple domain that will be automatically
# applied to each production deployment
resource "vercel_project_domain" "example" {
  project_id = vercel_project.example.id
  domain     = "i-love.vercel.app"
}
```

--------------------------------

### Create a Vercel Blob Project Connection

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/blob_project_connection.md

This example shows how to link an existing Blob store to a project and specify the environments where the connection should be active. Ensure the Blob store and project resources are defined prior to this.

```terraform
resource "vercel_blob_store" "example" {
  name = "example-blob-store"
}

resource "vercel_project" "example" {
  name = "example-blob-project"
}

resource "vercel_blob_project_connection" "example" {
  blob_store_id = vercel_blob_store.example.id
  project_id    = vercel_project.example.id
  environments  = ["preview", "production"]
}
```

--------------------------------

### Create a Redirecting Vercel Project Domain

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/project_domain.md

Example of creating a domain that redirects to another domain, with an optional status code. The redirect_status_code can be controlled.

```terraform
# A redirect of a domain name to a second domain name.
# The status_code can optionally be controlled.
resource "vercel_project_domain" "example_redirect" {
  project_id = vercel_project.example.id
  domain     = "i-also-love.vercel.app"

  redirect             = vercel_project_domain.example.domain
  redirect_status_code = 307
}
```

--------------------------------

### Create and Read Vercel Blob Store

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/blob_store.md

This example demonstrates how to create a Vercel Blob store using the `vercel_blob_store` resource and then read its details using the `vercel_blob_store` data source. The data source uses the ID of the created resource to fetch its information.

```terraform
resource "vercel_blob_store" "example" {
  name = "example-blob-store"
}

data "vercel_blob_store" "example" {
  id = vercel_blob_store.example.id
}
```

--------------------------------

### Create an Edge Config and apply a schema

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/edge_config_schema.md

This example shows how to create an Edge Config and then apply a JSON schema to it using the `vercel_edge_config_schema` resource. The schema is defined inline using a heredoc.

```terraform
resource "vercel_edge_config" "example" {
  name = "example"
}

resource "vercel_edge_config_schema" "example" {
  id         = vercel_edge_config.example.id
  definition = <<EOF
{
  "title": "Greeting",
  "type": "object",
  "properties": {
    "greeting": {
      "description": "A friendly greeting",
      "type": "string"
    }
  }
}
EOF
}
```

--------------------------------

### Example Usage of vercel_edge_config_item

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/edge_config_item.md

Demonstrates how to read a string item and a JSON item from an Edge Config. Ensure the Edge Config ID is correctly provided.

```terraform
data "vercel_edge_config" "example" {
  id = "ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}

# Read a string item
data "vercel_edge_config_item" "string_item" {
  id  = data.vercel_edge_config.example.id
  key = "foobar"
}

# Read a JSON item
data "vercel_edge_config_item" "json_item" {
  id  = data.vercel_edge_config.example.id
  key = "flags"
}
```

--------------------------------

### Install Local Vercel Terraform Provider

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/README.md

Execute this command to set up developer overrides in your Terraform configuration, allowing you to use a locally built provider binary.

```sh
task install
```

--------------------------------

### Example Usage of vercel_feature_flag_sdk_key Data Source

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/feature_flag_sdk_key.md

Use this data source to fetch details about a Feature Flag SDK Key. Ensure you provide the project ID and the SDK key's hash ID.

```terraform
data "vercel_feature_flag_sdk_key" "example" {
  project_id = "prj_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
  id         = "sdk_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
```

--------------------------------

### Example Usage of vercel_custom_environment Data Source

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/custom_environment.md

Use this data source to fetch details of an existing CustomEnvironment. It requires the project ID and the environment name. Ensure the Vercel project is defined.

```terraform
data "vercel_project" "example" {
  name = "example-project-with-custom-env"
}

data "vercel_custom_environment" "example" {
  project_id = data.vercel_project.example.id
  name       = "example-custom-env"
}
```

--------------------------------

### Example Usage of vercel_attack_challenge_mode Data Source

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/attack_challenge_mode.md

Use this data source to fetch the Attack Challenge Mode configuration for a specific project. Ensure the project ID is correctly provided.

```terraform
data "vercel_attack_challenge_mode" "example" {
  project_id = vercel_project.example.id
}
```

--------------------------------

### Example Usage of vercel_blob_store_secrets

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/blob_store_secrets.md

Use this data source to fetch the read/write token for a Blob store. Ensure the `vercel_blob_store` resource is defined first to obtain the `store_id`.

```terraform
resource "vercel_blob_store" "example" {
  name = "example-blob-store"
}

data "vercel_blob_store_secrets" "example" {
  store_id = vercel_blob_store.example.id
}
```

--------------------------------

### Example Usage of vercel_project_members Data Source

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/project_members.md

Use this data source to retrieve members and their roles for a Vercel Project. It requires the project ID, which can be obtained from the `vercel_project` data source.

```terraform
data "vercel_project" "example" {
  name = "example-with-members"
}

data "vercel_project_members" "example" {
  project_id = data.vercel_project.example.id
}
```

--------------------------------

### Get Vercel Blob Stores

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/blob_stores.md

Use this data source to list all available Blob stores for your Vercel account or a specified team. No additional setup is required beyond configuring the Vercel provider.

```terraform
data "vercel_blob_stores" "example" {}
```

--------------------------------

### Build Provider Documentation

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/README.md

Set Go environment variables and run the 'docs' task to build the provider's documentation. This generates markdown files for deployment.

```sh
export GOBIN=~/go/bin
export PATH=$GOBIN:$PATH
task docs
```

--------------------------------

### Deploying a prebuilt project

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/deployment.md

Use this configuration to deploy a prebuilt project. It requires both `vercel_project` and `vercel_prebuilt_project` data sources to be set up.

```terraform
data "vercel_project" "prebuilt_example" {
  name = "my-prebuilt-project"
}

data "vercel_prebuilt_project" "prebuilt_example" {
  path = "../ui"
}

resource "vercel_deployment" "prebuilt_example" {
  project_id  = data.vercel_project.prebuilt_example.id
  files       = data.vercel_prebuilt_project.prebuilt_example.output
  path_prefix = data.vercel_prebuilt_project.prebuilt_example.path
}
```

--------------------------------

### Build and Test Commands for Vercel Terraform Provider

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/AGENTS.md

Use these commands for building, testing, linting, and generating documentation for the provider.

```bash
task build
```

```bash
task test
```

```bash
task test -- -run 'TestAcc_Project*'
```

```bash
task lint
```

```bash
task docs
```

--------------------------------

### Build Vercel Terraform Provider

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/README.md

Run this command to build the provider plugin. It places the binary in the repository root.

```sh
task build
```

--------------------------------

### Import Configuration

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/firewall_config.md

Instructions on how to import an existing Vercel firewall configuration using the Terraform CLI.

```APIDOC
## Import

Import is supported using the following syntax:

The [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import) can be used, for example:

```shell
terraform import vercel_firewall_config.example team_xxxxxxxxxxxxxxxxxxxxxxxx/prj_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
```
```

--------------------------------

### Importing a vercel_microfrontend_group resource

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/microfrontend_group.md

These examples show how to import an existing Microfrontend Group resource into your Terraform state, either with or without a team ID.

```shell
# If importing into a personal account, or with a team configured on the provider, simply use the record id.
# - the microfrontend ID can be taken from the microfrontend settings page
terraform import vercel_microfrontend_group.example mfe_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
```

```shell
# Alternatively, you can import via the team_id and microfrontend_id.
# - team_id can be found in the team `settings` tab in the Vercel UI.
# - the microfrontend ID can be taken from the microfrontend settings page
terraform import vercel_microfrontend_group.example team_xxxxxxxxxxxxxxxxxxxxxxxx/mfe_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
```

--------------------------------

### Retrieve an Edge Config

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/edge_config.md

Use this data source to fetch details of an existing Edge Config by its ID. The ID must start with `ecfg_`.

```terraform
data "vercel_edge_config" "example" {
  id = "ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
```

--------------------------------

### Deploying files from a directory

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/deployment.md

Use this snippet to deploy files from a local directory. Ensure the `vercel_project` and `vercel_project_directory` data sources are configured correctly.

```terraform
data "vercel_project_directory" "files_example" {
  path = "../ui"
}

data "vercel_project" "files_example" {
  name = "my-awesome-project"
}

resource "vercel_deployment" "files_example" {
  project_id  = data.vercel_project.files_example.id
  files       = data.vercel_project_directory.files_example.files
  path_prefix = data.vercel_project_directory.files_example.path
  production  = true

  environment = {
    FOO = "bar"
  }
}
```

--------------------------------

### Example Usage of vercel_log_drain Data Source

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/log_drain.md

Use this data source to retrieve an existing log drain by its ID. Ensure the ID is correctly formatted.

```terraform
data "vercel_log_drain" "example" {
  id = "lg_xxxxxxx_xxxxxx_xxxxx"
}
```

--------------------------------

### Import a Feature Flag SDK Key

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/feature_flag_sdk_key.md

Demonstrates how to import an existing Feature Flag SDK Key into Terraform state, showing both team and non-team import syntaxes.

```shell
# If importing into a personal account, or with a team configured on
# the provider, simply use the project ID and SDK key hash.
# - project_id can be found in the project `settings` tab in the Vercel UI.
# - hash_key can be found from the Flags SDK Keys UI or API.
terraform import vercel_feature_flag_sdk_key.example prj_xxxxxxxxxxxxxxxxxxxxxxxxxxxx/sdk_xxxxxxxxxxxxxxxxxxxxxxxxxxxx

# Alternatively, you can import via the team_id, project_id, and SDK key hash.
# - team_id can be found in the team `settings` tab in the Vercel UI.
# - project_id can be found in the project `settings` tab in the Vercel UI.
terraform import vercel_feature_flag_sdk_key.example team_xxxxxxxxxxxxxxxxxxxxxxxx/prj_xxxxxxxxxxxxxxxxxxxxxxxxxxxx/sdk_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
```

--------------------------------

### Example Usage of vercel_edge_config_token

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/edge_config_token.md

Use this data source to retrieve information about an existing Edge Config Token. Ensure you provide the `edge_config_id` and `token` for authentication.

```terraform
data "vercel_edge_config_token" "test" {
  edge_config_id = "ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
  token          = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}
```

--------------------------------

### Get an existing Vercel project

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/project.md

Use this data source to fetch information about a pre-existing project on Vercel by its name. Ensure the project name is accurate.

```terraform
data "vercel_project" "example" {
  name = "my-existing-project"
}
```

--------------------------------

### vercel_project_rolling_release Data Source

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/project_rolling_release.md

Use the `vercel_project_rolling_release` data source to get the rolling release configuration of a Vercel project. You need to provide the `project_id` and optionally the `team_id`.

```APIDOC
## vercel_project_rolling_release (Data Source)

### Description

Data source for a Vercel project rolling release configuration.

### Method

GET

### Endpoint

`/v10/projects/{projectId}/rolling-release`

### Parameters

#### Path Parameters

- **projectId** (string) - Required - The ID of the project.

#### Query Parameters

- **teamId** (string) - Optional - The ID of the Vercel team.

### Response

#### Success Response (200)

- **advancement_type** (string) - The type of advancement for the rolling release. Either 'automatic' or 'manual-approval'.
- **stages** (array of objects) - The stages for the rolling release configuration.
  - **duration** (number) - The duration in minutes to wait before advancing to the next stage. Present for automatic advancement type.
  - **target_percentage** (number) - The percentage of traffic to route to this stage.

#### Response Example

```json
{
  "advancement_type": "automatic",
  "stages": [
    {
      "duration": 1440,
      "target_percentage": 10
    },
    {
      "duration": 1440,
      "target_percentage": 50
    },
    {
      "duration": 1440,
      "target_percentage": 100
    }
  ]
}
```
```

--------------------------------

### Create a Vercel Blob Object

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/blob_object.md

Use this resource to upload a local file to a Vercel Blob store. Ensure the `vercel_blob_store` resource is defined and its ID is referenced. The `source` path should point to the local file to be uploaded.

```terraform
resource "vercel_blob_store" "example" {
  name = "example-blob-store"
}

resource "vercel_blob_object" "example" {
  store_id              = vercel_blob_store.example.id
  pathname              = "branding/logo.svg"
  source                = "${path.module}/files/logo.svg"
  content_type          = "image/svg+xml"
  cache_control_max_age = 86400
}
```

--------------------------------

### Get Microfrontend Group - terraform-provider-vercel

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/microfrontend_group.md

Use this data source to retrieve information about an existing Microfrontend Group. Provide the group's ID to fetch its details.

```terraform
data "vercel_microfrontend_group" "example" {
  id = "mfe_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
```

--------------------------------

### Import a vercel_project_crons resource

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/project_crons.md

Import an existing vercel_project_crons resource using its project ID. If a team is configured on the provider, only the project ID is needed. Otherwise, include both team ID and project ID.

```shell
# If importing with a team configured on the provider, simply use the project ID.
# - project_id can be found in the project `settings` tab in the Vercel UI.
terraform import vercel_project_crons.example prj_xxxxxxxxxxxxxxxxxxxxxxxxxxxx

# Alternatively, you can import via the team_id and project_id.
# - team_id can be found in the team `settings` tab in the Vercel UI.
# - project_id can be found in the project `settings` tab in the Vercel UI.
terraform import vercel_project_crons.example team_xxxxxxxxxxxxxxxxxxxxxxxx/prj_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
```

--------------------------------

### Create an Expiring Vercel User Token

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/user_token.md

This example shows how to create a User Token that will automatically expire at a specified Unix timestamp in milliseconds. Ensure the timestamp is in the future.

```terraform
resource "vercel_user_token" "example_expiring" {
  name       = "example-expiring-token"
  expires_at = 1767225600000
}
```

--------------------------------

### Project Firewall Configuration

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/firewall_config.md

Configure the firewall settings for a Vercel project.

```APIDOC
## POST /api/projects/{projectId}/firewall

### Description
Configures the firewall settings for a specific Vercel project.

### Method
POST

### Endpoint
/api/projects/{projectId}/firewall

### Parameters
#### Path Parameters
- **projectId** (string) - Required - The ID of the project to configure.

#### Request Body
- **enabled** (Boolean) - Optional - Whether firewall is enabled or not.
- **ip_rules** (Block List) - Optional - IP rules to apply to the project.
  - **rule** (Block List) - Required - Nested IP rule configuration.
    - **action** (String) - Required - The action to take (e.g., block, allow).
    - **hostname** (String) - Required - Hosts to apply these rules to.
    - **ip** (String) - Required - IP address or CIDR to block.
    - **notes** (String) - Optional - Notes for the IP rule.
- **managed_rulesets** (Block) - Optional - The managed rulesets that are enabled.
  - **ai_bots** (Block) - Optional - Enable the ai_bots managed ruleset and select action.
    - **action** (String) - Optional - The action to take for AI bots.
    - **active** (Boolean) - Optional - Whether the AI bots ruleset is active.
  - **bot_filter** (Block) - Optional - DEPRECATED: Use bot_protection instead.
    - **action** (String) - Optional - The action to take for bot filtering.
    - **active** (Boolean) - Optional - Whether the bot filter is active.
  - **bot_protection** (Block) - Optional - Enable the bot_protection managed ruleset and select action.
    - **action** (String) - Optional - The action to take for bot protection.
    - **active** (Boolean) - Optional - Whether the bot protection is active.
  - **owasp** (Block) - Optional - Enable the OWASP managed rulesets and select ruleset behaviors.
    - **gen** (Attributes) - Optional - Generic Attack Detection.
      - **action** (String) - Required - The action to take.
      - **active** (Boolean) - Optional - Whether the rule is active.
    - **java** (Attributes) - Optional - Java Attack Detection.
      - **action** (String) - Required - The action to take.
      - **active** (Boolean) - Optional - Whether the rule is active.
    - **lfi** (Attributes) - Optional - Local File Inclusion Rules.
      - **action** (String) - Required - The action to take.
      - **active** (Boolean) - Optional - Whether the rule is active.
    - **ma** (Attributes) - Optional - Multipart Rules.
      - **action** (String) - Required - The action to take.
      - **active** (Boolean) - Optional - Whether the rule is active.
    - **php** (Attributes) - Optional - PHP Attack Detection.
      - **action** (String) - Required - The action to take.
      - **active** (Boolean) - Optional - Whether the rule is active.
    - **rce** (Attributes) - Optional - Remote Code Execution Rules.
      - **action** (String) - Required - The action to take.
      - **active** (Boolean) - Optional - Whether the rule is active.
    - **rfi** (Attributes) - Optional - Remote File Inclusion Rules.
      - **action** (String) - Required - The action to take.
      - **active** (Boolean) - Optional - Whether the rule is active.
    - **sd** (Attributes) - Optional - Scanner Detection Rules.
      - **action** (String) - Required - The action to take.
      - **active** (Boolean) - Optional - Whether the rule is active.
    - **sf** (Attributes) - Optional - Session Fixation Attack.
      - **action** (String) - Required - The action to take.
      - **active** (Boolean) - Optional - Whether the rule is active.
    - **sqli** (Attributes) - Optional - SQL Injection Rules.
      - **action** (String) - Required - The action to take.
      - **active** (Boolean) - Optional - Whether the rule is active.
    - **xss** (Attributes) - Optional - Cross Site Scripting Rules.
      - **action** (String) - Required - The action to take.
      - **active** (Boolean) - Optional - Whether the rule is active.
- **rules** (Block List) - Optional - Custom rules to apply to the project.
- **team_id** (String) - Optional - The ID of the team this project belongs to.

### Response
#### Success Response (200)
- **id** (String) - The unique identifier for this resource. Format: team_id/project_id.

#### Response Example
{
  "id": "team_abc123/project_xyz789"
}
```

--------------------------------

### Example Usage of vercel_feature_flag Data Source

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/feature_flag.md

Use this data source to read information about an existing Feature Flag. It requires the project ID and the stable flag key.

```terraform
data "vercel_feature_flag" "example" {
  project_id = "prj_xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
  key        = "checkout-redesign"
}
```

--------------------------------

### Get Vercel Deployment Information

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/deployment.md

Use this data source to read the details of an existing Vercel deployment by its ID or URL. Ensure the ID or URL is correctly specified.

```terraform
data "vercel_deployment" "example" {
  id = "https://my-vercel-project.vercel.app"
}
```

--------------------------------

### Example Usage of vercel_team_member Data Source

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/team_member.md

Use this data source to retrieve information about an existing Vercel team member. You must provide the user ID and the team ID.

```terraform
data "vercel_team_member" "example" {
  user_id = "uuuuuuuuuuuuuuuuuuuuuuuuuu"
  team_id = "team_xxxxxxxxxxxxxxxxxxxxxxxx"
}
```

--------------------------------

### Create Project and Environment Variables

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/project_environment_variables.md

Use this resource to define multiple environment variables for a Vercel project. Ensure sensitive values are explicitly set, with `false` for development and `true` for other environments if team policies enforce it.

```terraform
resource "vercel_project" "example" {
  name = "example-project"

  git_repository = {
    type = "github"
    repo = "vercel/some-repo"
  }
}

resource "vercel_project_environment_variables" "example" {
  project_id = vercel_project.example.id
  variables = [
    {
      key    = "SOME_VARIABLE"
      value  = "some_value"
      target = ["production", "preview"]
      sensitive = true
    },
    {
      key        = "ANOTHER_VARIABLE"
      value      = "another_value"
      git_branch = "staging"
      target     = ["preview"]
      sensitive  = true
    },
    {
      key       = "DEVELOPMENT_VARIABLE"
      value     = "development_value"
      target    = ["development"]
      sensitive = false
    }
  ]
}
```

--------------------------------

### Example Usage of vercel_endpoint_verification Data Source

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/data-sources/endpoint_verification.md

Use this data source to retrieve a verification code. This code should be set in the `x-vercel-verify` response header for your API to confirm endpoint ownership.

```terraform
data "vercel_endpoint_verification" "example" {}
```

--------------------------------

### Test Local Vercel Terraform Provider

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/README.md

Use these commands to test your local Terraform provider setup. 'terraform plan' and 'terraform apply' are standard Terraform CLI commands.

```sh
terraform plan
```

```sh
terraform apply
```

--------------------------------

### Create a TXT DNS Record

Source: https://github.com/vercel/terraform-provider-vercel/blob/main/docs/resources/dns_record.md

Use this to create a TXT record for a subdomain. The `value` can contain arbitrary text.

```terraform
resource "vercel_dns_record" "txt" {
  domain = "example.com"
  name   = "subdomain"
  type   = "TXT"
  ttl    = 60
  value  = "some text value"
}
```