Refresh self-hosted Visibility support guidance#4281
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📖 Docs PR preview links
|
3b4c9b9 to
1464ef5
Compare
|
Seems like a good opportunity to lump in this task and just do away with Standard Visibility in the docs. What do you think @bechols ? #3581 (comment) |
Certainly open to reducing the visibility (ha) of the legacy distinction. Does seem like we need to keep some reference, but it could be less prominent. What if I just move the legacy section to the bottom of the page? Also, if you know what this should look like, please take the branch and run with it. |
Addresses #3581 - standard Visibility was deprecated in v1.21 and removed in v1.24. This rewrites the conceptual Visibility page to treat current Visibility as the default, moves standard Visibility into a historical context callout, fixes ElasticSearch casing, and adds OpenSearch to the supported backends list. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Dustin Cote <dustin.cote@temporal.io>
|
resolves #3581 |
added some changes to accomplish this! |
|
Thanks @dustin-temporal this is great! |
|
|
||
| ## Legacy: standard Visibility {#standard-visibility} | ||
|
|
||
| :::info Historical context |
There was a problem hiding this comment.
I think this could just be paragraph text instead of in an admonition
|
|
||
| ## Legacy: standard Visibility {#standard-visibility} | ||
|
|
||
| :::info Historical context |
There was a problem hiding this comment.
| :::info Historical context |
Summary
Refresh the self-hosted Visibility page to reflect the current Visibility model and backend support story.
Changes
Validation
Why
The current page mixed current and legacy Visibility guidance and left the backend/version compatibility story ambiguous, especially for Cassandra, Elasticsearch, and OpenSearch.
┆Attachments: EDU-6037 Refresh self-hosted Visibility support guidance