docs(cre): add batch secret fetching for Go and TypeScript SDKs - #4057
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
👋 wentzeld, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
thodges-gh
previously approved these changes
Aug 13, 2026
russell-stern
requested changes
Aug 13, 2026
| If any secret in a batch fails to fetch, `getSecrets()` throws a `SecretsBatchError` containing all error messages from the failed secrets. | ||
| </Aside> | ||
|
|
||
| ### Using sequential fetch |
| If any secret in the batch fails to fetch, `GetSecrets()` returns an error containing all error messages from the failed secrets. | ||
| </Aside> | ||
|
|
||
| ### Using sequential fetch |
| If any secret in the batch fails to fetch, `GetSecrets()` returns an error containing all error messages from the failed secrets. | ||
| </Aside> | ||
|
|
||
| ### Using sequential fetch |
| If any secret in a batch fails to fetch, `getSecrets()` throws a `SecretsBatchError` containing all error messages from the failed secrets. | ||
| </Aside> | ||
|
|
||
| ### Using sequential fetch |
| ### `SecretsProvider` interface | ||
|
|
||
| The `SecretsProvider` interface is embedded in `Runtime`, which means `GetSecret` is available directly on the runtime object. It is also passed as a parameter to [`InitWorkflow`](#initworkflow), allowing you to access secrets during workflow initialization. | ||
| The `SecretsProvider` interface is embedded in `Runtime`, which means both `GetSecret` and `GetSecrets` are available directly on the runtime object. It is also passed as a parameter to [`InitWorkflow`](#initworkflow), allowing you to access secrets during workflow initialization. |
There was a problem hiding this comment.
You can get rid of the GetSecret reference here and below
| calling `.result()`. This is because `runInNodeMode` returns a function that can accept additional arguments. | ||
| </Aside> | ||
|
|
||
| ## `runtime.getSecret()` |
russell-stern
approved these changes
Aug 13, 2026
thodges-gh
approved these changes
Aug 14, 2026
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
4 participants
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
runtime.getSecrets()(TS) andruntime.GetSecrets()(Go) documentation to the SDK core reference pages, covering signatures, return types, error behavior, and examplesusing-secrets-batch-ts.ts,using-secrets-batch-go.go) used by the guide pagesTest plan
getSecrets/GetSecretssections appear correctly in the TS and Go SDK reference pagesSecretsProviderinterface block incore-go.mdxnow shows both methods