docs: lambda worker public preview#4663
Open
lennessyy wants to merge 28 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
lennessyy
changed the title
- Add Java SDK serverless worker docs (index + aws-lambda) - Add .NET SDK serverless worker docs (index + aws-lambda) - Add Java and .NET tabs to deploy guide - Update sidebar with new SDK sections - Change serverlessWorkers release stage from prerelease to publicPreview - Replace custom pre-release gating text with default ReleaseNoteHeader across all serverless pages
- Add snipsync markers to Java and .NET SDK pages referencing ea/aws-lambda branches - Update snipsync config to pull from ea/aws-lambda branches for samples-java and samples-dotnet - Update deploy guide Java tab to use builder pattern matching sample - Add Java sample link to deploy guide prerequisites
|
Deployment failed with the following error: Learn More: https://vercel.com/docs/concepts/projects/project-configuration |
…to create-function
…less pages - Use snipsync highlightedLines to highlight key lines in code samples - Replace hand-written .NET code block with snipsync selectedLines snippet - Improve .NET intro text to match Go/Python/TS pattern - Remove redundant bypass code block from .NET configure section - Update config file resolution wording across all SDKs
- Rewrite Java and .NET intro text to explain the code pattern before showing it - Fix deploy guide link to point to aws-lambda subpage across all SDKs - Update config file resolution wording across all SDKs - Align Java deploy guide with sample repo: java17 runtime, direct JAR upload, correct handler format, 1024 MB memory, 90s timeout - Remove unnecessary copy/re-zip step for Java shadow JAR - Remove redundant bypass code block from .NET configure section - Fix OTel description wording in Java page
- Fix Java build section: shadow JAR uploads directly, no re-zip needed - Use placeholder matching actual shadow JAR naming pattern - Update runtime to java17, memory to 1024, timeout to 90 - Fix handler format to include ::handleRequest - Improve Java SDK page intro text and link to registration docs - Simplify OTel configure description - Remove eager activities sentence from Java defaults table - Fix deploy guide link to aws-lambda subpage
- Troubleshooting: restructure Validate Connection section to match UI error messages (no compute config, connection invalid, task queue not registered), remove standalone WCI detecting Tasks section - Deploy guide: add Launch Stack button blurb, add Connection status to verify step - Encyclopedia: add ramping link to versioning constraint
# Conflicts: # docs/encyclopedia/workers/serverless-workers.mdx # docs/production-deployment/worker-deployments/serverless-workers/aws-lambda.mdx
Quoting exact UI strings makes the docs brittle to UI copy changes. Use a bulleted list with short labels instead.
02strich
reviewed
Jul 1, 2026
| | Workflow duration | No limit. Workflows of any duration work, regardless of the invocation timeout. A Workflow runs across as many invocations as needed. | | ||
| | Worker code | Same Temporal SDK Worker code, using the serverless Worker package for your SDK. | | ||
| | Versioning | [Worker Versioning](/worker-versioning) is required. Each Workflow must have an `AutoUpgrade` or `Pinned` behavior, set per-Workflow or as a Worker-level default. See [Worker Versioning with Serverless Workers](#worker-versioning-with-serverless-workers). | | ||
| | Versioning | [Worker Versioning](/worker-versioning) is required. Each Workflow must have an `AutoUpgrade` or `Pinned` behavior, set per-Workflow or as a Worker-level default. For rollout strategies including ramping, see [Worker Versioning](/worker-versioning). See [Worker Versioning with Serverless Workers](#worker-versioning-with-serverless-workers). | |
Contributor
There was a problem hiding this comment.
nit: the two 'see ...' callouts sound quite similar - can we make this a bit nicer?
Java SDK tracing goes through the OpenTracing interceptor bridged into OpenTelemetry's data model, not a native OTel tracing interceptor. The trace structure is expected to change when native support ships.
The Worker Controller Instance invokes compute providers using region-scoped identifiers (for example, a Lambda ARN). Workflows replicate to the standby region on failover, but the WCI keeps invoking the original region's Worker instead of following the Namespace to the new active region.
State the operational consequence first (workloads may keep hitting a degraded region after failover) before explaining why (compute provider configuration is region-scoped).
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| Encrypt sensitive values like TLS keys or API keys. Refer to [AWS documentation](https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars-encryption.html) for options. | ||
|
|
||
| ### TLS/CA loading on Lambda {/* #tls-ca-loading */} |
Contributor
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Temporal.Headings] 'TLS/CA loading on Lambda ***********************' should use sentence-style capitalization.
- Consolidate the two similar "see" callouts on the Versioning constraint row into one, per @02strich's review comment on #4663. - Add an intro sentence under "Related considerations" instead of stacking it directly against the Serverless Workers subheading. - Fix a broken anchor link to the removed "Check that the WCI is detecting Tasks" troubleshooting section, reintroduced by merging main; point it at the current Validate Connection section instead.
Duncanma
added
the
blocked-on-release
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.
What does this PR do?
Prepares serverless worker docs for Lambda public preview.
Deploy guide (
aws-lambda.mdx)Troubleshooting page (
troubleshooting/serverless-workers.mdx)Encyclopedia page (
serverless-workers.mdx)Notes to reviewers
┆Attachments: EDU-6480 docs: terraform for serverless worker