UpdateProjectProjectsEnv

July 24, 2026 ยท View on GitHub

Example Usage

import { UpdateProjectProjectsEnv } from "@vercel/sdk/models/updateprojectbranchmatcher.js";

let value: UpdateProjectProjectsEnv = {
  type: "secret",
  value: "<value>",
  key: "<key>",
};

Fields

FieldTypeRequiredDescription
targetmodels.UpdateProjectProjectsTarget:heavy_minus_sign:N/A
typemodels.UpdateProjectProjectsType:heavy_check_mark:N/A
sunsetSecretIdstring:heavy_minus_sign:This is used to identify variables that have been migrated from type secret to sensitive.
legacyValuestring:heavy_minus_sign:Legacy now-encryption ciphertext, present after migration swaps value/vsmValue
decryptedboolean:heavy_minus_sign:N/A
valuestring:heavy_check_mark:N/A
vsmValuestring:heavy_minus_sign:N/A
idstring:heavy_minus_sign:N/A
keystring:heavy_check_mark:N/A
configurationIdstring:heavy_minus_sign:N/A
createdAtnumber:heavy_minus_sign:N/A
updatedAtnumber:heavy_minus_sign:N/A
createdBystring:heavy_minus_sign:N/A
updatedBystring:heavy_minus_sign:N/A
gitBranchstring:heavy_minus_sign:N/A
visibilitymodels.UpdateProjectVisibility:heavy_minus_sign:User-facing config/secret model. When set, authoritative for new code paths when the env-var-config-secret-ui flag is enabled. Legacy rows omit this field; legacy rows omit it and callers fall back to existing type behavior.
edgeConfigIdstring:heavy_minus_sign:N/A
edgeConfigTokenIdstring:heavy_minus_sign:N/A
contentHintmodels.UpdateProjectContentHint:heavy_minus_sign:N/A
internalContentHintmodels.UpdateProjectInternalContentHint:heavy_minus_sign:Similar to contentHints, but should not be exposed to the user.
commentstring:heavy_minus_sign:N/A
customEnvironmentIdsstring[]:heavy_minus_sign:N/A