Add Vercel KMS support - #557
Draft
marcgreenstock wants to merge 1 commit into
Draft
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Terraform support for managing Vercel KMS, which previously had no
provider coverage — issuers, their signing keys, project-grant policies, and
self-signed certificates could only be managed via the dashboard or API. This
lets users manage the full KMS lifecycle as code.
vercel_kms_issuer(resource + data source) — JWT issuer with a JWKSendpoint;
nameis mutable, key material is immutable/computed. Supportsimporting an external private key.
vercel_kms_issuer_policy— project-grant policies authorizing a project torequest signed tokens in given environments, with optional token claims.
vercel_kms_signing_key— models an imperative key rotation via akeeperstrigger; keys retire on the next rotation (no single-key delete API).
vercel_kms_certificate— mints an ephemeral self-signed X.509 certificate;generate-on-create with a
keeperstrigger, no server-side read/delete.Validation
behind
VERCEL_TERRAFORM_TESTING_KMS=trueon a KMS-enabled team. The issuertest covers create → import → rename; the signing-key and certificate tests
assert that changing
keepersproduces a new key id / serial number.Made with Cursor