Repository navigation
Conversation
Clarify that SecretsConcurrencyLimit counts in-flight fetch calls, and that a single or batch call each counts as one against Secrets.CallLimit. Document the 10-secret cap per batch fetch and per cre secrets file. Add a Fetching multiple secrets section to the deployed secrets guide, note that Confidential Workflows share the same limits, and fix the Go SDK example namespace. Add troubleshooting entries for namespace mismatches, batch size, partly missing batches, the call limit and the generic closing hints on secrets errors. Update lastModified dates.
Add a Secrets limits at a glance section and cross-references that explain the 100-secret storage limit, the 10-secret upload limit per cre secrets file, and the 10-secret batch fetch limit are separate limits.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Remove repeated limit numbers from the secrets guides, CLI reference and confidential workflow guides. Those pages now describe which limits exist and link to Service Quotas, so the values only need updating in one place.
wentzeld
marked this pull request as ready for review
October 30, 2026 04:42
This branch was successfully deployed
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
Documents the limits that apply to CRE secrets. The values live only on the Service Quotas page. Other pages describe the limit in words and link
there, so there is one place to update.
fetch call. Added the per-request secrets limit (
VaultRequestBatchSizeLimit) and an Aside that explains how the stored, per-upload, per-batch-fetchand per-execution limits differ.
Troubleshooting entries for namespace mismatch, batch size, a partly missing batch, the call limit (including how it appears on confidential workflows)
and the generic closing hints on secrets errors.
Notes for reviewers
VaultRequestBatchSizeLimitis the internal setting name for the per-request limit. Please confirm it should appear in public docs.known bug, so please drop that line once it is fixed.