Vercel v1.14.3 published on Monday, Oct 7, 2024 by Pulumiverse
vercel.getProject
Explore with Pulumi AI
Provides information about an existing project within Vercel.
A Project groups deployments and custom domains. To deploy on Vercel, you need a Project.
For more detailed information, please see the Vercel documentation.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as vercel from "@pulumi/vercel";
const foo = vercel.getProject({
name: "my-existing-project",
});
export const projectId = foo.then(foo => foo.id);
import pulumi
import pulumi_vercel as vercel
foo = vercel.get_project(name="my-existing-project")
pulumi.export("projectId", foo.id)
package main
import (
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
"github.com/pulumiverse/pulumi-vercel/sdk/go/vercel"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
foo, err := vercel.LookupProject(ctx, &vercel.LookupProjectArgs{
Name: "my-existing-project",
}, nil)
if err != nil {
return err
}
ctx.Export("projectId", foo.Id)
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Vercel = Pulumi.Vercel;
return await Deployment.RunAsync(() =>
{
var foo = Vercel.GetProject.Invoke(new()
{
Name = "my-existing-project",
});
return new Dictionary<string, object?>
{
["projectId"] = foo.Apply(getProjectResult => getProjectResult.Id),
};
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.vercel.VercelFunctions;
import com.pulumi.vercel.inputs.GetProjectArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var foo = VercelFunctions.getProject(GetProjectArgs.builder()
.name("my-existing-project")
.build());
ctx.export("projectId", foo.applyValue(getProjectResult -> getProjectResult.id()));
}
}
variables:
foo:
fn::invoke:
Function: vercel:getProject
Arguments:
name: my-existing-project
outputs:
# Outputs prj_xxxxxx
projectId: ${foo.id}
Using getProject
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getProject(args: GetProjectArgs, opts?: InvokeOptions): Promise<GetProjectResult>
function getProjectOutput(args: GetProjectOutputArgs, opts?: InvokeOptions): Output<GetProjectResult>
def get_project(name: Optional[str] = None,
team_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetProjectResult
def get_project_output(name: Optional[pulumi.Input[str]] = None,
team_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetProjectResult]
func LookupProject(ctx *Context, args *LookupProjectArgs, opts ...InvokeOption) (*LookupProjectResult, error)
func LookupProjectOutput(ctx *Context, args *LookupProjectOutputArgs, opts ...InvokeOption) LookupProjectResultOutput
> Note: This function is named LookupProject
in the Go SDK.
public static class GetProject
{
public static Task<GetProjectResult> InvokeAsync(GetProjectArgs args, InvokeOptions? opts = null)
public static Output<GetProjectResult> Invoke(GetProjectInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetProjectResult> getProject(GetProjectArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: vercel:index/getProject:getProject
arguments:
# arguments dictionary
The following arguments are supported:
getProject Result
The following output properties are available:
- Auto
Assign boolCustom Domains - Automatically assign custom production domains after each Production deployment via merge to the production branch or Vercel CLI deploy with --prod. Defaults to
true
- Automatically
Expose boolSystem Environment Variables - Vercel provides a set of Environment Variables that are automatically populated by the System, such as the URL of the Deployment or the name of the Git branch deployed. To expose them to your Deployments, enable this field
- Build
Command string - The build command for this project. If omitted, this value will be automatically detected.
- Customer
Success boolCode Visibility - Allows Vercel Customer Support to inspect all Deployments' source code in this project to assist with debugging.
- Dev
Command string - The dev command for this project. If omitted, this value will be automatically detected.
- Directory
Listing bool - If no index file is present within a directory, the directory contents will be displayed.
- Environments
List<Pulumiverse.
Vercel. Outputs. Get Project Environment> - A list of environment variables that should be configured for the project.
- Framework string
- The framework that is being used for this project. If omitted, no framework is selected.
- Function
Failover bool - Automatically failover Serverless Functions to the nearest region. You can customize regions through vercel.json. A new Deployment is required for your changes to take effect.
- Git
Comments Pulumiverse.Vercel. Outputs. Get Project Git Comments - Configuration for Git Comments.
- Git
Fork boolProtection - Ensures that pull requests targeting your Git repository must be authorized by a member of your Team before deploying if your Project has Environment Variables or if the pull request includes a change to vercel.json.
- Git
Lfs bool - Enables Git LFS support. Git LFS replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.
- Git
Repository Pulumiverse.Vercel. Outputs. Get Project Git Repository - The Git Repository that will be connected to the project. When this is defined, any pushes to the specified connected Git Repository will be automatically deployed. This requires the corresponding Vercel for Github, Gitlab or Bitbucket plugins to be installed.
- Id string
- The ID of this resource.
- Ignore
Command string - When a commit is pushed to the Git repository that is connected with your Project, its SHA will determine if a new Build has to be issued. If the SHA was deployed before, no new Build will be issued. You can customize this behavior with a command that exits with code 1 (new Build needed) or code 0.
- Install
Command string - The install command for this project. If omitted, this value will be automatically detected.
- Name string
- The name of the project.
- Oidc
Token Pulumiverse.Config Vercel. Outputs. Get Project Oidc Token Config - Configuration for OpenID Connect (OIDC) tokens.
- Options
Allowlist Pulumiverse.Vercel. Outputs. Get Project Options Allowlist - Disable Deployment Protection for CORS preflight
OPTIONS
requests for a list of paths. - Output
Directory string - The output directory of the project. When null is used this value will be automatically detected.
- Password
Protection Pulumiverse.Vercel. Outputs. Get Project Password Protection - Ensures visitors of your Preview Deployments must enter a password in order to gain access.
- Preview
Comments bool - Whether comments are enabled on your Preview Deployments.
- Prioritise
Production boolBuilds - If enabled, builds for the Production environment will be prioritized over Preview environments.
- Protection
Bypass boolFor Automation - Allows automation services to bypass Vercel Authentication and Password Protection for both Preview and Production Deployments on this project when using an HTTP header named
x-vercel-protection-bypass
. - Public
Source bool - Specifies whether the source code and logs of the deployments for this project should be public or not.
- Resource
Config Pulumiverse.Vercel. Outputs. Get Project Resource Config - Resource Configuration for the project.
- Root
Directory string - The name of a directory or relative path to the source code of your project. When null is used it will default to the project root.
- Serverless
Function stringRegion - The region on Vercel's network to which your Serverless Functions are deployed. It should be close to any data source your Serverless Function might depend on. A new Deployment is required for your changes to take effect. Please see Vercel's documentation for a full list of regions.
- Skew
Protection string - Ensures that outdated clients always fetch the correct version for a given deployment. This value defines how long Vercel keeps Skew Protection active.
- Team
Id string - The team ID the project exists beneath. Required when configuring a team resource if a default team has not been set in the provider.
- Trusted
Ips Pulumiverse.Vercel. Outputs. Get Project Trusted Ips - Ensures only visitors from an allowed IP address can access your deployment.
- Vercel
Authentication Pulumiverse.Vercel. Outputs. Get Project Vercel Authentication - Ensures visitors to your Preview Deployments are logged into Vercel and have a minimum of Viewer access on your team.
- Auto
Assign boolCustom Domains - Automatically assign custom production domains after each Production deployment via merge to the production branch or Vercel CLI deploy with --prod. Defaults to
true
- Automatically
Expose boolSystem Environment Variables - Vercel provides a set of Environment Variables that are automatically populated by the System, such as the URL of the Deployment or the name of the Git branch deployed. To expose them to your Deployments, enable this field
- Build
Command string - The build command for this project. If omitted, this value will be automatically detected.
- Customer
Success boolCode Visibility - Allows Vercel Customer Support to inspect all Deployments' source code in this project to assist with debugging.
- Dev
Command string - The dev command for this project. If omitted, this value will be automatically detected.
- Directory
Listing bool - If no index file is present within a directory, the directory contents will be displayed.
- Environments
[]Get
Project Environment - A list of environment variables that should be configured for the project.
- Framework string
- The framework that is being used for this project. If omitted, no framework is selected.
- Function
Failover bool - Automatically failover Serverless Functions to the nearest region. You can customize regions through vercel.json. A new Deployment is required for your changes to take effect.
- Git
Comments GetProject Git Comments - Configuration for Git Comments.
- Git
Fork boolProtection - Ensures that pull requests targeting your Git repository must be authorized by a member of your Team before deploying if your Project has Environment Variables or if the pull request includes a change to vercel.json.
- Git
Lfs bool - Enables Git LFS support. Git LFS replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.
- Git
Repository GetProject Git Repository - The Git Repository that will be connected to the project. When this is defined, any pushes to the specified connected Git Repository will be automatically deployed. This requires the corresponding Vercel for Github, Gitlab or Bitbucket plugins to be installed.
- Id string
- The ID of this resource.
- Ignore
Command string - When a commit is pushed to the Git repository that is connected with your Project, its SHA will determine if a new Build has to be issued. If the SHA was deployed before, no new Build will be issued. You can customize this behavior with a command that exits with code 1 (new Build needed) or code 0.
- Install
Command string - The install command for this project. If omitted, this value will be automatically detected.
- Name string
- The name of the project.
- Oidc
Token GetConfig Project Oidc Token Config - Configuration for OpenID Connect (OIDC) tokens.
- Options
Allowlist GetProject Options Allowlist - Disable Deployment Protection for CORS preflight
OPTIONS
requests for a list of paths. - Output
Directory string - The output directory of the project. When null is used this value will be automatically detected.
- Password
Protection GetProject Password Protection - Ensures visitors of your Preview Deployments must enter a password in order to gain access.
- Preview
Comments bool - Whether comments are enabled on your Preview Deployments.
- Prioritise
Production boolBuilds - If enabled, builds for the Production environment will be prioritized over Preview environments.
- Protection
Bypass boolFor Automation - Allows automation services to bypass Vercel Authentication and Password Protection for both Preview and Production Deployments on this project when using an HTTP header named
x-vercel-protection-bypass
. - Public
Source bool - Specifies whether the source code and logs of the deployments for this project should be public or not.
- Resource
Config GetProject Resource Config - Resource Configuration for the project.
- Root
Directory string - The name of a directory or relative path to the source code of your project. When null is used it will default to the project root.
- Serverless
Function stringRegion - The region on Vercel's network to which your Serverless Functions are deployed. It should be close to any data source your Serverless Function might depend on. A new Deployment is required for your changes to take effect. Please see Vercel's documentation for a full list of regions.
- Skew
Protection string - Ensures that outdated clients always fetch the correct version for a given deployment. This value defines how long Vercel keeps Skew Protection active.
- Team
Id string - The team ID the project exists beneath. Required when configuring a team resource if a default team has not been set in the provider.
- Trusted
Ips GetProject Trusted Ips - Ensures only visitors from an allowed IP address can access your deployment.
- Vercel
Authentication GetProject Vercel Authentication - Ensures visitors to your Preview Deployments are logged into Vercel and have a minimum of Viewer access on your team.
- auto
Assign BooleanCustom Domains - Automatically assign custom production domains after each Production deployment via merge to the production branch or Vercel CLI deploy with --prod. Defaults to
true
- automatically
Expose BooleanSystem Environment Variables - Vercel provides a set of Environment Variables that are automatically populated by the System, such as the URL of the Deployment or the name of the Git branch deployed. To expose them to your Deployments, enable this field
- build
Command String - The build command for this project. If omitted, this value will be automatically detected.
- customer
Success BooleanCode Visibility - Allows Vercel Customer Support to inspect all Deployments' source code in this project to assist with debugging.
- dev
Command String - The dev command for this project. If omitted, this value will be automatically detected.
- directory
Listing Boolean - If no index file is present within a directory, the directory contents will be displayed.
- environments
List<Get
Project Environment> - A list of environment variables that should be configured for the project.
- framework String
- The framework that is being used for this project. If omitted, no framework is selected.
- function
Failover Boolean - Automatically failover Serverless Functions to the nearest region. You can customize regions through vercel.json. A new Deployment is required for your changes to take effect.
- git
Comments GetProject Git Comments - Configuration for Git Comments.
- git
Fork BooleanProtection - Ensures that pull requests targeting your Git repository must be authorized by a member of your Team before deploying if your Project has Environment Variables or if the pull request includes a change to vercel.json.
- git
Lfs Boolean - Enables Git LFS support. Git LFS replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.
- git
Repository GetProject Git Repository - The Git Repository that will be connected to the project. When this is defined, any pushes to the specified connected Git Repository will be automatically deployed. This requires the corresponding Vercel for Github, Gitlab or Bitbucket plugins to be installed.
- id String
- The ID of this resource.
- ignore
Command String - When a commit is pushed to the Git repository that is connected with your Project, its SHA will determine if a new Build has to be issued. If the SHA was deployed before, no new Build will be issued. You can customize this behavior with a command that exits with code 1 (new Build needed) or code 0.
- install
Command String - The install command for this project. If omitted, this value will be automatically detected.
- name String
- The name of the project.
- oidc
Token GetConfig Project Oidc Token Config - Configuration for OpenID Connect (OIDC) tokens.
- options
Allowlist GetProject Options Allowlist - Disable Deployment Protection for CORS preflight
OPTIONS
requests for a list of paths. - output
Directory String - The output directory of the project. When null is used this value will be automatically detected.
- password
Protection GetProject Password Protection - Ensures visitors of your Preview Deployments must enter a password in order to gain access.
- preview
Comments Boolean - Whether comments are enabled on your Preview Deployments.
- prioritise
Production BooleanBuilds - If enabled, builds for the Production environment will be prioritized over Preview environments.
- protection
Bypass BooleanFor Automation - Allows automation services to bypass Vercel Authentication and Password Protection for both Preview and Production Deployments on this project when using an HTTP header named
x-vercel-protection-bypass
. - public
Source Boolean - Specifies whether the source code and logs of the deployments for this project should be public or not.
- resource
Config GetProject Resource Config - Resource Configuration for the project.
- root
Directory String - The name of a directory or relative path to the source code of your project. When null is used it will default to the project root.
- serverless
Function StringRegion - The region on Vercel's network to which your Serverless Functions are deployed. It should be close to any data source your Serverless Function might depend on. A new Deployment is required for your changes to take effect. Please see Vercel's documentation for a full list of regions.
- skew
Protection String - Ensures that outdated clients always fetch the correct version for a given deployment. This value defines how long Vercel keeps Skew Protection active.
- team
Id String - The team ID the project exists beneath. Required when configuring a team resource if a default team has not been set in the provider.
- trusted
Ips GetProject Trusted Ips - Ensures only visitors from an allowed IP address can access your deployment.
- vercel
Authentication GetProject Vercel Authentication - Ensures visitors to your Preview Deployments are logged into Vercel and have a minimum of Viewer access on your team.
- auto
Assign booleanCustom Domains - Automatically assign custom production domains after each Production deployment via merge to the production branch or Vercel CLI deploy with --prod. Defaults to
true
- automatically
Expose booleanSystem Environment Variables - Vercel provides a set of Environment Variables that are automatically populated by the System, such as the URL of the Deployment or the name of the Git branch deployed. To expose them to your Deployments, enable this field
- build
Command string - The build command for this project. If omitted, this value will be automatically detected.
- customer
Success booleanCode Visibility - Allows Vercel Customer Support to inspect all Deployments' source code in this project to assist with debugging.
- dev
Command string - The dev command for this project. If omitted, this value will be automatically detected.
- directory
Listing boolean - If no index file is present within a directory, the directory contents will be displayed.
- environments
Get
Project Environment[] - A list of environment variables that should be configured for the project.
- framework string
- The framework that is being used for this project. If omitted, no framework is selected.
- function
Failover boolean - Automatically failover Serverless Functions to the nearest region. You can customize regions through vercel.json. A new Deployment is required for your changes to take effect.
- git
Comments GetProject Git Comments - Configuration for Git Comments.
- git
Fork booleanProtection - Ensures that pull requests targeting your Git repository must be authorized by a member of your Team before deploying if your Project has Environment Variables or if the pull request includes a change to vercel.json.
- git
Lfs boolean - Enables Git LFS support. Git LFS replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.
- git
Repository GetProject Git Repository - The Git Repository that will be connected to the project. When this is defined, any pushes to the specified connected Git Repository will be automatically deployed. This requires the corresponding Vercel for Github, Gitlab or Bitbucket plugins to be installed.
- id string
- The ID of this resource.
- ignore
Command string - When a commit is pushed to the Git repository that is connected with your Project, its SHA will determine if a new Build has to be issued. If the SHA was deployed before, no new Build will be issued. You can customize this behavior with a command that exits with code 1 (new Build needed) or code 0.
- install
Command string - The install command for this project. If omitted, this value will be automatically detected.
- name string
- The name of the project.
- oidc
Token GetConfig Project Oidc Token Config - Configuration for OpenID Connect (OIDC) tokens.
- options
Allowlist GetProject Options Allowlist - Disable Deployment Protection for CORS preflight
OPTIONS
requests for a list of paths. - output
Directory string - The output directory of the project. When null is used this value will be automatically detected.
- password
Protection GetProject Password Protection - Ensures visitors of your Preview Deployments must enter a password in order to gain access.
- preview
Comments boolean - Whether comments are enabled on your Preview Deployments.
- prioritise
Production booleanBuilds - If enabled, builds for the Production environment will be prioritized over Preview environments.
- protection
Bypass booleanFor Automation - Allows automation services to bypass Vercel Authentication and Password Protection for both Preview and Production Deployments on this project when using an HTTP header named
x-vercel-protection-bypass
. - public
Source boolean - Specifies whether the source code and logs of the deployments for this project should be public or not.
- resource
Config GetProject Resource Config - Resource Configuration for the project.
- root
Directory string - The name of a directory or relative path to the source code of your project. When null is used it will default to the project root.
- serverless
Function stringRegion - The region on Vercel's network to which your Serverless Functions are deployed. It should be close to any data source your Serverless Function might depend on. A new Deployment is required for your changes to take effect. Please see Vercel's documentation for a full list of regions.
- skew
Protection string - Ensures that outdated clients always fetch the correct version for a given deployment. This value defines how long Vercel keeps Skew Protection active.
- team
Id string - The team ID the project exists beneath. Required when configuring a team resource if a default team has not been set in the provider.
- trusted
Ips GetProject Trusted Ips - Ensures only visitors from an allowed IP address can access your deployment.
- vercel
Authentication GetProject Vercel Authentication - Ensures visitors to your Preview Deployments are logged into Vercel and have a minimum of Viewer access on your team.
- auto_
assign_ boolcustom_ domains - Automatically assign custom production domains after each Production deployment via merge to the production branch or Vercel CLI deploy with --prod. Defaults to
true
- automatically_
expose_ boolsystem_ environment_ variables - Vercel provides a set of Environment Variables that are automatically populated by the System, such as the URL of the Deployment or the name of the Git branch deployed. To expose them to your Deployments, enable this field
- build_
command str - The build command for this project. If omitted, this value will be automatically detected.
- customer_
success_ boolcode_ visibility - Allows Vercel Customer Support to inspect all Deployments' source code in this project to assist with debugging.
- dev_
command str - The dev command for this project. If omitted, this value will be automatically detected.
- directory_
listing bool - If no index file is present within a directory, the directory contents will be displayed.
- environments
Sequence[Get
Project Environment] - A list of environment variables that should be configured for the project.
- framework str
- The framework that is being used for this project. If omitted, no framework is selected.
- function_
failover bool - Automatically failover Serverless Functions to the nearest region. You can customize regions through vercel.json. A new Deployment is required for your changes to take effect.
- git_
comments GetProject Git Comments - Configuration for Git Comments.
- git_
fork_ boolprotection - Ensures that pull requests targeting your Git repository must be authorized by a member of your Team before deploying if your Project has Environment Variables or if the pull request includes a change to vercel.json.
- git_
lfs bool - Enables Git LFS support. Git LFS replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.
- git_
repository GetProject Git Repository - The Git Repository that will be connected to the project. When this is defined, any pushes to the specified connected Git Repository will be automatically deployed. This requires the corresponding Vercel for Github, Gitlab or Bitbucket plugins to be installed.
- id str
- The ID of this resource.
- ignore_
command str - When a commit is pushed to the Git repository that is connected with your Project, its SHA will determine if a new Build has to be issued. If the SHA was deployed before, no new Build will be issued. You can customize this behavior with a command that exits with code 1 (new Build needed) or code 0.
- install_
command str - The install command for this project. If omitted, this value will be automatically detected.
- name str
- The name of the project.
- oidc_
token_ Getconfig Project Oidc Token Config - Configuration for OpenID Connect (OIDC) tokens.
- options_
allowlist GetProject Options Allowlist - Disable Deployment Protection for CORS preflight
OPTIONS
requests for a list of paths. - output_
directory str - The output directory of the project. When null is used this value will be automatically detected.
- password_
protection GetProject Password Protection - Ensures visitors of your Preview Deployments must enter a password in order to gain access.
- preview_
comments bool - Whether comments are enabled on your Preview Deployments.
- prioritise_
production_ boolbuilds - If enabled, builds for the Production environment will be prioritized over Preview environments.
- protection_
bypass_ boolfor_ automation - Allows automation services to bypass Vercel Authentication and Password Protection for both Preview and Production Deployments on this project when using an HTTP header named
x-vercel-protection-bypass
. - public_
source bool - Specifies whether the source code and logs of the deployments for this project should be public or not.
- resource_
config GetProject Resource Config - Resource Configuration for the project.
- root_
directory str - The name of a directory or relative path to the source code of your project. When null is used it will default to the project root.
- serverless_
function_ strregion - The region on Vercel's network to which your Serverless Functions are deployed. It should be close to any data source your Serverless Function might depend on. A new Deployment is required for your changes to take effect. Please see Vercel's documentation for a full list of regions.
- skew_
protection str - Ensures that outdated clients always fetch the correct version for a given deployment. This value defines how long Vercel keeps Skew Protection active.
- team_
id str - The team ID the project exists beneath. Required when configuring a team resource if a default team has not been set in the provider.
- trusted_
ips GetProject Trusted Ips - Ensures only visitors from an allowed IP address can access your deployment.
- vercel_
authentication GetProject Vercel Authentication - Ensures visitors to your Preview Deployments are logged into Vercel and have a minimum of Viewer access on your team.
- auto
Assign BooleanCustom Domains - Automatically assign custom production domains after each Production deployment via merge to the production branch or Vercel CLI deploy with --prod. Defaults to
true
- automatically
Expose BooleanSystem Environment Variables - Vercel provides a set of Environment Variables that are automatically populated by the System, such as the URL of the Deployment or the name of the Git branch deployed. To expose them to your Deployments, enable this field
- build
Command String - The build command for this project. If omitted, this value will be automatically detected.
- customer
Success BooleanCode Visibility - Allows Vercel Customer Support to inspect all Deployments' source code in this project to assist with debugging.
- dev
Command String - The dev command for this project. If omitted, this value will be automatically detected.
- directory
Listing Boolean - If no index file is present within a directory, the directory contents will be displayed.
- environments List<Property Map>
- A list of environment variables that should be configured for the project.
- framework String
- The framework that is being used for this project. If omitted, no framework is selected.
- function
Failover Boolean - Automatically failover Serverless Functions to the nearest region. You can customize regions through vercel.json. A new Deployment is required for your changes to take effect.
- git
Comments Property Map - Configuration for Git Comments.
- git
Fork BooleanProtection - Ensures that pull requests targeting your Git repository must be authorized by a member of your Team before deploying if your Project has Environment Variables or if the pull request includes a change to vercel.json.
- git
Lfs Boolean - Enables Git LFS support. Git LFS replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.
- git
Repository Property Map - The Git Repository that will be connected to the project. When this is defined, any pushes to the specified connected Git Repository will be automatically deployed. This requires the corresponding Vercel for Github, Gitlab or Bitbucket plugins to be installed.
- id String
- The ID of this resource.
- ignore
Command String - When a commit is pushed to the Git repository that is connected with your Project, its SHA will determine if a new Build has to be issued. If the SHA was deployed before, no new Build will be issued. You can customize this behavior with a command that exits with code 1 (new Build needed) or code 0.
- install
Command String - The install command for this project. If omitted, this value will be automatically detected.
- name String
- The name of the project.
- oidc
Token Property MapConfig - Configuration for OpenID Connect (OIDC) tokens.
- options
Allowlist Property Map - Disable Deployment Protection for CORS preflight
OPTIONS
requests for a list of paths. - output
Directory String - The output directory of the project. When null is used this value will be automatically detected.
- password
Protection Property Map - Ensures visitors of your Preview Deployments must enter a password in order to gain access.
- preview
Comments Boolean - Whether comments are enabled on your Preview Deployments.
- prioritise
Production BooleanBuilds - If enabled, builds for the Production environment will be prioritized over Preview environments.
- protection
Bypass BooleanFor Automation - Allows automation services to bypass Vercel Authentication and Password Protection for both Preview and Production Deployments on this project when using an HTTP header named
x-vercel-protection-bypass
. - public
Source Boolean - Specifies whether the source code and logs of the deployments for this project should be public or not.
- resource
Config Property Map - Resource Configuration for the project.
- root
Directory String - The name of a directory or relative path to the source code of your project. When null is used it will default to the project root.
- serverless
Function StringRegion - The region on Vercel's network to which your Serverless Functions are deployed. It should be close to any data source your Serverless Function might depend on. A new Deployment is required for your changes to take effect. Please see Vercel's documentation for a full list of regions.
- skew
Protection String - Ensures that outdated clients always fetch the correct version for a given deployment. This value defines how long Vercel keeps Skew Protection active.
- team
Id String - The team ID the project exists beneath. Required when configuring a team resource if a default team has not been set in the provider.
- trusted
Ips Property Map - Ensures only visitors from an allowed IP address can access your deployment.
- vercel
Authentication Property Map - Ensures visitors to your Preview Deployments are logged into Vercel and have a minimum of Viewer access on your team.
Supporting Types
GetProjectEnvironment
- Git
Branch string - The git branch of the environment variable.
- Id string
- The ID of the environment variable
- Key string
- The name of the environment variable.
- Sensitive bool
- Whether the Environment Variable is sensitive or not. Note that the value will be
null
for sensitive environment variables. - Targets List<string>
- The environments that the environment variable should be present on. Valid targets are either
production
,preview
, ordevelopment
. - Value string
- The value of the environment variable.
- Git
Branch string - The git branch of the environment variable.
- Id string
- The ID of the environment variable
- Key string
- The name of the environment variable.
- Sensitive bool
- Whether the Environment Variable is sensitive or not. Note that the value will be
null
for sensitive environment variables. - Targets []string
- The environments that the environment variable should be present on. Valid targets are either
production
,preview
, ordevelopment
. - Value string
- The value of the environment variable.
- git
Branch String - The git branch of the environment variable.
- id String
- The ID of the environment variable
- key String
- The name of the environment variable.
- sensitive Boolean
- Whether the Environment Variable is sensitive or not. Note that the value will be
null
for sensitive environment variables. - targets List<String>
- The environments that the environment variable should be present on. Valid targets are either
production
,preview
, ordevelopment
. - value String
- The value of the environment variable.
- git
Branch string - The git branch of the environment variable.
- id string
- The ID of the environment variable
- key string
- The name of the environment variable.
- sensitive boolean
- Whether the Environment Variable is sensitive or not. Note that the value will be
null
for sensitive environment variables. - targets string[]
- The environments that the environment variable should be present on. Valid targets are either
production
,preview
, ordevelopment
. - value string
- The value of the environment variable.
- git_
branch str - The git branch of the environment variable.
- id str
- The ID of the environment variable
- key str
- The name of the environment variable.
- sensitive bool
- Whether the Environment Variable is sensitive or not. Note that the value will be
null
for sensitive environment variables. - targets Sequence[str]
- The environments that the environment variable should be present on. Valid targets are either
production
,preview
, ordevelopment
. - value str
- The value of the environment variable.
- git
Branch String - The git branch of the environment variable.
- id String
- The ID of the environment variable
- key String
- The name of the environment variable.
- sensitive Boolean
- Whether the Environment Variable is sensitive or not. Note that the value will be
null
for sensitive environment variables. - targets List<String>
- The environments that the environment variable should be present on. Valid targets are either
production
,preview
, ordevelopment
. - value String
- The value of the environment variable.
GetProjectGitComments
- On
Commit bool - Whether Commit comments are enabled
- On
Pull boolRequest - Whether Pull Request comments are enabled
- On
Commit bool - Whether Commit comments are enabled
- On
Pull boolRequest - Whether Pull Request comments are enabled
- on
Commit Boolean - Whether Commit comments are enabled
- on
Pull BooleanRequest - Whether Pull Request comments are enabled
- on
Commit boolean - Whether Commit comments are enabled
- on
Pull booleanRequest - Whether Pull Request comments are enabled
- on_
commit bool - Whether Commit comments are enabled
- on_
pull_ boolrequest - Whether Pull Request comments are enabled
- on
Commit Boolean - Whether Commit comments are enabled
- on
Pull BooleanRequest - Whether Pull Request comments are enabled
GetProjectGitRepository
- Deploy
Hooks List<Pulumiverse.Vercel. Inputs. Get Project Git Repository Deploy Hook> - Deploy hooks are unique URLs that allow you to trigger a deployment of a given branch. See https://vercel.com/docs/deployments/deploy-hooks for full information.
- Production
Branch string - By default, every commit pushed to the main branch will trigger a Production Deployment instead of the usual Preview Deployment. You can switch to a different branch here.
- Repo string
- The name of the git repository. For example:
vercel/next.js
. - Type string
- The git provider of the repository. Must be either
github
,gitlab
, orbitbucket
.
- Deploy
Hooks []GetProject Git Repository Deploy Hook - Deploy hooks are unique URLs that allow you to trigger a deployment of a given branch. See https://vercel.com/docs/deployments/deploy-hooks for full information.
- Production
Branch string - By default, every commit pushed to the main branch will trigger a Production Deployment instead of the usual Preview Deployment. You can switch to a different branch here.
- Repo string
- The name of the git repository. For example:
vercel/next.js
. - Type string
- The git provider of the repository. Must be either
github
,gitlab
, orbitbucket
.
- deploy
Hooks List<GetProject Git Repository Deploy Hook> - Deploy hooks are unique URLs that allow you to trigger a deployment of a given branch. See https://vercel.com/docs/deployments/deploy-hooks for full information.
- production
Branch String - By default, every commit pushed to the main branch will trigger a Production Deployment instead of the usual Preview Deployment. You can switch to a different branch here.
- repo String
- The name of the git repository. For example:
vercel/next.js
. - type String
- The git provider of the repository. Must be either
github
,gitlab
, orbitbucket
.
- deploy
Hooks GetProject Git Repository Deploy Hook[] - Deploy hooks are unique URLs that allow you to trigger a deployment of a given branch. See https://vercel.com/docs/deployments/deploy-hooks for full information.
- production
Branch string - By default, every commit pushed to the main branch will trigger a Production Deployment instead of the usual Preview Deployment. You can switch to a different branch here.
- repo string
- The name of the git repository. For example:
vercel/next.js
. - type string
- The git provider of the repository. Must be either
github
,gitlab
, orbitbucket
.
- deploy_
hooks Sequence[GetProject Git Repository Deploy Hook] - Deploy hooks are unique URLs that allow you to trigger a deployment of a given branch. See https://vercel.com/docs/deployments/deploy-hooks for full information.
- production_
branch str - By default, every commit pushed to the main branch will trigger a Production Deployment instead of the usual Preview Deployment. You can switch to a different branch here.
- repo str
- The name of the git repository. For example:
vercel/next.js
. - type str
- The git provider of the repository. Must be either
github
,gitlab
, orbitbucket
.
- deploy
Hooks List<Property Map> - Deploy hooks are unique URLs that allow you to trigger a deployment of a given branch. See https://vercel.com/docs/deployments/deploy-hooks for full information.
- production
Branch String - By default, every commit pushed to the main branch will trigger a Production Deployment instead of the usual Preview Deployment. You can switch to a different branch here.
- repo String
- The name of the git repository. For example:
vercel/next.js
. - type String
- The git provider of the repository. Must be either
github
,gitlab
, orbitbucket
.
GetProjectGitRepositoryDeployHook
GetProjectOidcTokenConfig
- Enabled bool
- When true, Vercel issued OpenID Connect (OIDC) tokens will be available on the compute environments. See https://vercel.com/docs/security/secure-backend-access/oidc for more information.
- Enabled bool
- When true, Vercel issued OpenID Connect (OIDC) tokens will be available on the compute environments. See https://vercel.com/docs/security/secure-backend-access/oidc for more information.
- enabled Boolean
- When true, Vercel issued OpenID Connect (OIDC) tokens will be available on the compute environments. See https://vercel.com/docs/security/secure-backend-access/oidc for more information.
- enabled boolean
- When true, Vercel issued OpenID Connect (OIDC) tokens will be available on the compute environments. See https://vercel.com/docs/security/secure-backend-access/oidc for more information.
- enabled bool
- When true, Vercel issued OpenID Connect (OIDC) tokens will be available on the compute environments. See https://vercel.com/docs/security/secure-backend-access/oidc for more information.
- enabled Boolean
- When true, Vercel issued OpenID Connect (OIDC) tokens will be available on the compute environments. See https://vercel.com/docs/security/secure-backend-access/oidc for more information.
GetProjectOptionsAllowlist
- Paths
List<Pulumiverse.
Vercel. Inputs. Get Project Options Allowlist Path> - The allowed paths for the OPTIONS Allowlist. Incoming requests will bypass Deployment Protection if they have the method
OPTIONS
and start with one of the path values.
- Paths
[]Get
Project Options Allowlist Path - The allowed paths for the OPTIONS Allowlist. Incoming requests will bypass Deployment Protection if they have the method
OPTIONS
and start with one of the path values.
- paths
List<Get
Project Options Allowlist Path> - The allowed paths for the OPTIONS Allowlist. Incoming requests will bypass Deployment Protection if they have the method
OPTIONS
and start with one of the path values.
- paths
Get
Project Options Allowlist Path[] - The allowed paths for the OPTIONS Allowlist. Incoming requests will bypass Deployment Protection if they have the method
OPTIONS
and start with one of the path values.
- paths
Sequence[Get
Project Options Allowlist Path] - The allowed paths for the OPTIONS Allowlist. Incoming requests will bypass Deployment Protection if they have the method
OPTIONS
and start with one of the path values.
- paths List<Property Map>
- The allowed paths for the OPTIONS Allowlist. Incoming requests will bypass Deployment Protection if they have the method
OPTIONS
and start with one of the path values.
GetProjectOptionsAllowlistPath
- Value string
- Value string
- value String
- value string
- value str
- value String
GetProjectPasswordProtection
- Deployment
Type string - The deployment environment that will be protected.
- Deployment
Type string - The deployment environment that will be protected.
- deployment
Type String - The deployment environment that will be protected.
- deployment
Type string - The deployment environment that will be protected.
- deployment_
type str - The deployment environment that will be protected.
- deployment
Type String - The deployment environment that will be protected.
GetProjectResourceConfig
- Function
Default stringCpu Type - The amount of CPU available to your Serverless Functions. Should be one of 'standard_legacy' (0.6vCPU), 'standard' (1vCPU) or 'performance' (1.7vCPUs).
- Function
Default intTimeout - The default timeout for Serverless Functions.
- Function
Default stringCpu Type - The amount of CPU available to your Serverless Functions. Should be one of 'standard_legacy' (0.6vCPU), 'standard' (1vCPU) or 'performance' (1.7vCPUs).
- Function
Default intTimeout - The default timeout for Serverless Functions.
- function
Default StringCpu Type - The amount of CPU available to your Serverless Functions. Should be one of 'standard_legacy' (0.6vCPU), 'standard' (1vCPU) or 'performance' (1.7vCPUs).
- function
Default IntegerTimeout - The default timeout for Serverless Functions.
- function
Default stringCpu Type - The amount of CPU available to your Serverless Functions. Should be one of 'standard_legacy' (0.6vCPU), 'standard' (1vCPU) or 'performance' (1.7vCPUs).
- function
Default numberTimeout - The default timeout for Serverless Functions.
- function_
default_ strcpu_ type - The amount of CPU available to your Serverless Functions. Should be one of 'standard_legacy' (0.6vCPU), 'standard' (1vCPU) or 'performance' (1.7vCPUs).
- function_
default_ inttimeout - The default timeout for Serverless Functions.
- function
Default StringCpu Type - The amount of CPU available to your Serverless Functions. Should be one of 'standard_legacy' (0.6vCPU), 'standard' (1vCPU) or 'performance' (1.7vCPUs).
- function
Default NumberTimeout - The default timeout for Serverless Functions.
GetProjectTrustedIps
- Addresses
List<Pulumiverse.
Vercel. Inputs. Get Project Trusted Ips Address> - The allowed IP addressses and CIDR ranges with optional descriptions.
- Deployment
Type string - The deployment environment that will be protected.
- Protection
Mode string - Whether or not Trusted IPs is required or optional to access a deployment.
- Addresses
[]Get
Project Trusted Ips Address - The allowed IP addressses and CIDR ranges with optional descriptions.
- Deployment
Type string - The deployment environment that will be protected.
- Protection
Mode string - Whether or not Trusted IPs is required or optional to access a deployment.
- addresses
List<Get
Project Trusted Ips Address> - The allowed IP addressses and CIDR ranges with optional descriptions.
- deployment
Type String - The deployment environment that will be protected.
- protection
Mode String - Whether or not Trusted IPs is required or optional to access a deployment.
- addresses
Get
Project Trusted Ips Address[] - The allowed IP addressses and CIDR ranges with optional descriptions.
- deployment
Type string - The deployment environment that will be protected.
- protection
Mode string - Whether or not Trusted IPs is required or optional to access a deployment.
- addresses
Sequence[Get
Project Trusted Ips Address] - The allowed IP addressses and CIDR ranges with optional descriptions.
- deployment_
type str - The deployment environment that will be protected.
- protection_
mode str - Whether or not Trusted IPs is required or optional to access a deployment.
- addresses List<Property Map>
- The allowed IP addressses and CIDR ranges with optional descriptions.
- deployment
Type String - The deployment environment that will be protected.
- protection
Mode String - Whether or not Trusted IPs is required or optional to access a deployment.
GetProjectTrustedIpsAddress
GetProjectVercelAuthentication
- Deployment
Type string - The deployment environment that will be protected.
- Deployment
Type string - The deployment environment that will be protected.
- deployment
Type String - The deployment environment that will be protected.
- deployment
Type string - The deployment environment that will be protected.
- deployment_
type str - The deployment environment that will be protected.
- deployment
Type String - The deployment environment that will be protected.
Package Details
- Repository
- vercel pulumiverse/pulumi-vercel
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
vercel
Terraform Provider.