[cli] optional override of existing environment variables

[mountainash]

Why

Closes #11130

Changelog

Added --force argument to upsert existing environment variables (#11130)

References

• Vercel API /v10/projects/{idOrName}/env https://vercel.com/docs/rest-api/endpoints/projects#create-one-or-more-environment-variables

[changeset-bot]

🦋 Changeset detected

Latest commit: 7f785fd

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
vercel	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[EndangeredMassa]

Thanks for the detailed PR with tests! I think we can accept this change if we make some tweaks.

[EndangeredMassa]

I made some tweaks to flesh out the new option.

[mountainash]

All valid to me. Thanks. 🙏

[EndangeredMassa]

Thanks @mountainash!

[crbraun]

Is it possible this caused an issue using env variables? Just recently I am no longer able to call my Dynamo endpoint

Error fetching item from DynamoDB UnrecognizedClientException: The security token included in the request is invalid

   const dynamoClient: DynamoDBClient = new DynamoDBClient({region: AWS_REGION});
    // Use GetItemCommand to get the item from the table
    const {Item} = await dynamoClient.send(new GetItemCommand(params));

Works in my local env. Verified my env variables have not changed. Both AWS_SECRET_ACCESS_KEY and AWS_ACCESS_KEY_ID exist and are populated with the correct key.

[EndangeredMassa]

@crbraun what version of the Vercel CLI (vercel) are you using? Can you verify that the env var is available at that time in your code by logging it out?

[crbraun]

@crbraun what version of the Vercel CLI (vercel) are you using? Can you verify that the env var is available at that time in your code by logging it out?

I did verify that AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY are present. Oddly there there is a AWS_SESSION_TOKEN present in the environment which my application never sets. I expect this is the issue. But I am not sure how this got in the environment as I do not have this variable set anywhere.

[crbraun]

I was able to work around this issue by adding an empty AWS_SESSION_TOKEN env variable to my environment. I expect there is something wrong with the vercel deployer as it seems to be setting an AWS_SESSION_TOKEN when there is none present in the configuration.

[EndangeredMassa]

Hrm. I don't think that should be happening. If you open a support case, we can look into it. https://vercel.com/contact

[crbraun]

It doesn't look like I am allowed to create a support ticket

Visit our Community for further help or create a paid account for dedicated Builds & Deployments → Builds support.

I have it worked around for now, but I am fairly certain there was a recent change in vercel that was deployed today that caused this issue. Let me know if there is a way I can log an issue with support, be glad to do so.

-- Thanks