docs(temporal-proxy): add Temporal Proxy configuration page#4954
Open
pseudomuto wants to merge 2 commits into
Open
docs(temporal-proxy): add Temporal Proxy configuration page#4954pseudomuto wants to merge 2 commits into
pseudomuto wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| Credentials require TLS to the upstream. If you set `credentials` without a `tls` block, the configuration fails to | ||
| load. | ||
|
|
||
| ### Configure TLS |
Contributor
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Temporal.Headings] 'Configure TLS' should use sentence-style capitalization.
Author
There was a problem hiding this comment.
I don't think this applies here since TLS is an acronym
Contributor
📖 Docs PR preview links
|
Add a deploy to production page for the Temporal Proxy, the gRPC proxy that routes SDK Client and Worker traffic to one or more upstream Temporal Services (local, self-hosted, or Temporal Cloud) while handling Namespace translation, TLS, and credentials. The proxy is pre-release, so the page leads with that caveat and links to the repository, the Cloud example, and the Helm chart for the definitive, still-evolving schema. Lives under production-deployment as a directory (index.mdx) to leave room for future pages; the slug is pinned so the URL is stable regardless of file location.
pseudomuto
force-pushed
the
temporal_proxy_overview
branch
from
July 24, 2026 17:19
eec71b6 to
02a7493
Compare
Contributor
|
@flippedcoder should we remove that slug, following our new guidance? And should this use the release note header to communicate the pre-release status? |
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
2 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.
Add a deploy-to-production page for the Temporal Proxy, the gRPC proxy that routes SDK Client and Worker traffic to one or more upstream Temporal Services (local, self-hosted, or Temporal Cloud) while handling Namespace translation, TLS, and credentials.
The proxy is pre-release, so the page leads with that caveat and links to the repository, the Cloud example, and the Helm chart for the definitive, still-evolving schema. Lives under production-deployment as a directory (index.mdx) to leave room for future pages; the slug is pinned so the URL is stable regardless of file location.
┆Attachments: EDU-6796 docs(temporal-proxy): add Temporal Proxy configuration page