diff --git a/COMPONENTS.md b/COMPONENTS.md index 1b98786152..59b8ad11ed 100644 --- a/COMPONENTS.md +++ b/COMPONENTS.md @@ -20,6 +20,7 @@ Whether you’re using core components or experimenting with new ones, this guid - [Using Components in MDX Source Files](#using-components-in-mdx-source-files) - [Using CaptionedImage](#using-captionedimage) - [Using DiscoverableDisclosure](#using-discoverabledisclosure) +- [Using ReleaseStage](#using-releasestage) - [Using DocsTable](#using-docstable) - [Using PhotoCarousel](#using-photocarousel) - [Using RelatedRead](#using-relatedread) @@ -170,6 +171,59 @@ Usage: An additional `prompt` prop enables you to specify the leading text. Normally it defaults to `prompt = "Dive deeper — "`. +## Using ReleaseStage + +Role: Standardized callout for features in Pre-release or Public Preview. + +General Availability features do not need a callout - GA is the default/assumed state. + +Usage: + +``` + +``` + +This renders a `:::tip Support, stability, and dependency info` callout with the text: +"Provisioned Capacity is in [Public Preview](/evaluate/development-production-features/release-stages#public-preview)." + +### Props + +- **`stage`** (optional): `"pre-release"` | `"public-preview"`. Determines the release stage link and label. +- **`feature`** (optional): The feature name. Used to generate the callout text (e.g. "Feature X is in Public Preview."). +- **`verb`** (optional): Defaults to `"is"`. Set to `"are"` for plural feature names. +- **`children`** (optional): Additional content shown below the auto-generated text, or the entire callout body for custom callouts. + +If you use the auto-generated text, pass a `feature`. There is no generic no-feature mode. + +### With additional context + +``` + +All APIs are experimental and may be subject to backwards-incompatible changes. + +``` + +### Plural feature names + +``` + +``` + +### Children-only mode + +For complex cases where the auto-generated text doesn't fit: + +``` + +Same-region Replication and Multi-cloud Replication are in +[Public Preview](/evaluate/development-production-features/release-stages#public-preview). + +``` + ## Using DocsTable In certain rare instances, standard Markdown tables won't work for our needs. diff --git a/docs/cloud/capacity-modes.mdx b/docs/cloud/capacity-modes.mdx index 89641f8533..4db4c020e9 100644 --- a/docs/cloud/capacity-modes.mdx +++ b/docs/cloud/capacity-modes.mdx @@ -27,6 +27,8 @@ tags: - TRUs --- +import { ReleaseStage } from '@site/src/components'; + Each Namespace in Temporal has a rate limit, which is measured in [Actions](/cloud/pricing#action) per second. Temporal offers two different modes for adjusting capacity: On-Demand Capacity or Provisioned Capacity. With On-Demand Capacity, Namespace capacity is increased automatically along with usage. @@ -101,12 +103,10 @@ Actions that are external to the core Temporal service do not contribute to your Using On-Demand Capacity, your rate limit grows automatically along with your usage. - | | Actions Per Second | Requests Per Second | Operations Per Second| |---------------|--------------------|---------------------|----------------------| | Default Limit | 500 | 2000 | 4000 | - Scaling automatically adjusts based on the lesser of 4 * APS Average or 2 * APS P90 over the past 7 days. If you experience usage spikes, you may hit a throughput limit. @@ -133,11 +133,7 @@ This means that your default limit would be 800 APS. ## Provisioned Capacity {#provisioned-capacity} -:::tip Support, stability, and dependency info - -Provisioned Capacity is currently in [Public Preview](/evaluate/development-production-features/release-stages#public-preview). - -::: + Provisioned Capacity provides an alternative to On-Demand Capacity by allowing you to control the limits on your Namespace based on your specific need. @@ -166,7 +162,6 @@ The amount of capacity available within a region may vary. Temporal will check available capacity at the time of your request and aims to provision requested capacity within two minutes. If you need capacity beyond what is self-serviceable or available in a region, please [file a support ticket](https://docs.temporal.io/cloud/support#ticketing) indicating the limit, region, and timeframe that the capacity is needed. - ### When should I use Provisioned Capacity? Provisioned Capacity works well when you’re aware of specific increases in load on your Namespace. For example: diff --git a/docs/cloud/connectivity/index.mdx b/docs/cloud/connectivity/index.mdx index 78ae0fd3e5..90df907624 100644 --- a/docs/cloud/connectivity/index.mdx +++ b/docs/cloud/connectivity/index.mdx @@ -18,7 +18,7 @@ keywords: - term --- -import { ToolTipTerm, DiscoverableDisclosure, CaptionedImage, SdkTabs } from '@site/src/components'; +import { CaptionedImage, DiscoverableDisclosure, ReleaseStage, SdkTabs, ToolTipTerm } from '@site/src/components'; import { LANGUAGE_TAB_GROUP, getLanguageLabel } from '@site/src/constants/languageTabs'; ## Private network connectivity for namespaces @@ -57,11 +57,7 @@ For step 3, keep reading for details on [connectivity rules](/cloud/connectivity ## Connectivity rules -:::tip Support, stability, and dependency info - -Connectivity rules are currently in [public preview](/evaluate/development-production-features/release-stages#public-preview). - -::: + :::info Web UI Connectivity @@ -177,7 +173,6 @@ tcld namespace set-connectivity-rules --namespace "my-namespace.abc123" --remove [Example in the Terraform repo](https://github.com/temporalio/terraform-provider-temporalcloud/tree/main/examples/resources/temporalcloud_namespace/resource.tf#L113-L128) - ## View the connectivity rules for a namespace You have two ways to view the connectivity rules attached to a particular namespace. diff --git a/docs/cloud/high-availability/index.mdx b/docs/cloud/high-availability/index.mdx index 10bcd57b7c..775622c0f8 100644 --- a/docs/cloud/high-availability/index.mdx +++ b/docs/cloud/high-availability/index.mdx @@ -18,7 +18,7 @@ keywords: - temporal-cloud --- -import { ToolTipTerm, DiscoverableDisclosure, CaptionedImage } from '@site/src/components'; +import { CaptionedImage, DiscoverableDisclosure, ToolTipTerm } from '@site/src/components'; Temporal Cloud's High Availability features use asynchronous across multiple to provide enhanced resilience and a 99.99% [SLA](/cloud/sla). When you enable High Availability features, Temporal deploys your primary and its in separate isolation domains, giving you control over the location of both. This redundancy, combined with capability, enhances availability during outages. diff --git a/docs/cloud/metrics/openmetrics/api-reference.mdx b/docs/cloud/metrics/openmetrics/api-reference.mdx index 59dd2c0dfe..b50aa5a33c 100644 --- a/docs/cloud/metrics/openmetrics/api-reference.mdx +++ b/docs/cloud/metrics/openmetrics/api-reference.mdx @@ -25,7 +25,6 @@ import { CaptionedImage } from '@site/src/components'; The Temporal Cloud OpenMetrics API provides actionable operational metrics about your Temporal Cloud deployment. This is a scrapable HTTP API that returns metrics in OpenMetrics format, suitable for ingestion by Prometheus-compatible monitoring systems. - ## Available Metrics Reference Metrics descriptions are also available programmatically via the `/v1/descriptors` endpoint. You can see the Metrics Reference for a list of available metrics. @@ -309,7 +308,6 @@ scrape_configs: ::: - ### Label Management #### Prometheus diff --git a/docs/cloud/metrics/openmetrics/index.mdx b/docs/cloud/metrics/openmetrics/index.mdx index 563e1ef2fb..6fde959453 100644 --- a/docs/cloud/metrics/openmetrics/index.mdx +++ b/docs/cloud/metrics/openmetrics/index.mdx @@ -22,7 +22,6 @@ tags: - Temporal Cloud --- - :::tip PRICING Future pricing may apply to high-volume usage that exceeds standard [limits](/cloud/metrics/openmetrics/api-reference#api-limits). diff --git a/docs/cloud/metrics/openmetrics/metrics-integrations.mdx b/docs/cloud/metrics/openmetrics/metrics-integrations.mdx index ddc4724c08..900b60818a 100644 --- a/docs/cloud/metrics/openmetrics/metrics-integrations.mdx +++ b/docs/cloud/metrics/openmetrics/metrics-integrations.mdx @@ -27,7 +27,6 @@ Metrics can be exported from Temporal Cloud using the OpenMetrics endpoint. This This document is for basic configuration only. For advanced concepts such as label management and high cardinality scenarios see the [general API reference](/cloud/metrics/openmetrics/api-reference). - ## Integrations ### Datadog diff --git a/docs/cloud/metrics/openmetrics/metrics-reference.mdx b/docs/cloud/metrics/openmetrics/metrics-reference.mdx index 0b52ca688d..7bf8f86f87 100644 --- a/docs/cloud/metrics/openmetrics/metrics-reference.mdx +++ b/docs/cloud/metrics/openmetrics/metrics-reference.mdx @@ -23,7 +23,6 @@ tags: This document describes all metrics available from the Temporal Cloud OpenMetrics endpoint. - ## Metric Conventions ### Metric Types diff --git a/docs/cloud/metrics/openmetrics/migration-guide.mdx b/docs/cloud/metrics/openmetrics/migration-guide.mdx index 99431b677e..5edffa79f7 100644 --- a/docs/cloud/metrics/openmetrics/migration-guide.mdx +++ b/docs/cloud/metrics/openmetrics/migration-guide.mdx @@ -21,8 +21,7 @@ tags: - Temporal Cloud --- -import { RelatedReadContainer, RelatedReadItem } from '@site/src/components'; -import { CaptionedImage } from '@site/src/components'; +import { CaptionedImage, RelatedReadContainer, RelatedReadItem, ReleaseStage } from '@site/src/components'; Temporal Cloud is transitioning from our Prometheus query endpoint to an industry-standard OpenMetrics (Prometheus-compatible) endpoint for metrics collection. This migration represents a significant improvement in how you diff --git a/docs/cloud/migrate/automated.mdx b/docs/cloud/migrate/automated.mdx index 7ba7a89a7d..e21e6d8689 100644 --- a/docs/cloud/migrate/automated.mdx +++ b/docs/cloud/migrate/automated.mdx @@ -18,12 +18,9 @@ tags: - Production --- -:::tip Support, stability, and dependency info +import { ReleaseStage } from '@site/src/components'; -Automated migration is currently in [Pre-release](/evaluate/development-production-features/release-stages#pre-release). -Please contact your Temporal account executive prior to planning your migration project. - -::: + ## Process Overview diff --git a/docs/cloud/nexus/index.mdx b/docs/cloud/nexus/index.mdx index e287d7c1b3..e8245b3110 100644 --- a/docs/cloud/nexus/index.mdx +++ b/docs/cloud/nexus/index.mdx @@ -25,13 +25,6 @@ tags: import { CaptionedImage } from '@site/src/components'; -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal Nexus is now [Generally Available](/evaluate/development-production-features/release-stages#general-availability). -Learn why you should use Nexus in the [evaluation guide](/evaluate/nexus). - -::: - Temporal Cloud builds on the [core Nexus experience](/nexus) with: - **Global [Nexus Registry](/nexus/registry)** - Scoped to your entire Account across all Namespaces. Workers in any Namespace can host Nexus Services for others to use. diff --git a/docs/cloud/nexus/latency-availability.mdx b/docs/cloud/nexus/latency-availability.mdx index 7da8a3ee23..eab78dd106 100644 --- a/docs/cloud/nexus/latency-availability.mdx +++ b/docs/cloud/nexus/latency-availability.mdx @@ -20,13 +20,6 @@ keywords: - service level agreement --- -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal Nexus is now [Generally Available](/evaluate/development-production-features/release-stages#general-availability). -Learn why you should use Nexus in the [evaluation guide](/evaluate/nexus). - -::: - Nexus latency and availability in Temporal Cloud: - **SLOs and SLAs** - Nexus operations (for example, `RespondWorkflowTaskCompleted`, `PollNexusTaskQueue`, `RespondNexusTaskCompleted`, and `RespondNexusTaskFailed`) have the same [latency SLOs](/cloud/service-availability#latency) and [availability SLAs](/cloud/sla) as other Worker requests in both caller and handler Namespaces. diff --git a/docs/cloud/nexus/limits.mdx b/docs/cloud/nexus/limits.mdx index ae5aa96c21..6027318ae1 100644 --- a/docs/cloud/nexus/limits.mdx +++ b/docs/cloud/nexus/limits.mdx @@ -18,13 +18,6 @@ keywords: - max operation duration --- -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal Nexus is now [Generally Available](/evaluate/development-production-features/release-stages#general-availability). -Learn why you should use Nexus in the [evaluation guide](/evaluate/nexus). - -::: - Nexus limits are documented in [Temporal Cloud limits](/cloud/limits): - [Nexus rate limits](/cloud/limits#nexus-rate-limits) - Nexus requests count toward the Namespace RPS limit. diff --git a/docs/cloud/nexus/observability.mdx b/docs/cloud/nexus/observability.mdx index 7344a60bb7..5f910fb35e 100644 --- a/docs/cloud/nexus/observability.mdx +++ b/docs/cloud/nexus/observability.mdx @@ -17,14 +17,6 @@ keywords: - audit log streaming --- -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal Nexus is now -[Generally Available](/evaluate/development-production-features/release-stages#general-availability). Learn why you -should use Nexus in the [evaluation guide](/evaluate/nexus). - -::: - Nexus observability in Temporal Cloud: - **[Nexus metrics](/nexus/metrics)** - [SDK metrics](/nexus/metrics#sdk-metrics) emitted by Workers and [Cloud metrics](/nexus/metrics#cloud-metrics) emitted by Temporal Cloud. diff --git a/docs/cloud/nexus/pricing.mdx b/docs/cloud/nexus/pricing.mdx index 785d9b4227..53bdf1eb23 100644 --- a/docs/cloud/nexus/pricing.mdx +++ b/docs/cloud/nexus/pricing.mdx @@ -13,13 +13,6 @@ keywords: - Temporal Cloud pricing --- -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal Nexus is now [Generally Available](/evaluate/development-production-features/release-stages#general-availability). -Learn why you should use Nexus in the [evaluation guide](/evaluate/nexus). - -::: - Nexus pricing: - **One Action to start or cancel a Nexus Operation** in the caller Namespace. diff --git a/docs/cloud/nexus/security.mdx b/docs/cloud/nexus/security.mdx index cfab97c6e3..6541f7f768 100644 --- a/docs/cloud/nexus/security.mdx +++ b/docs/cloud/nexus/security.mdx @@ -14,13 +14,6 @@ keywords: - access control --- -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal Nexus is now [Generally Available](/evaluate/development-production-features/release-stages#general-availability). -Learn why you should use Nexus in the [evaluation guide](/evaluate/nexus). - -::: - Nexus security in Temporal Cloud: - **[Runtime access controls](/nexus/security#runtime-access-controls)** - Endpoint allowlists restrict which caller Namespaces can use an Endpoint. See [configuring access controls](/nexus/registry#configure-runtime-access-controls). diff --git a/docs/cloud/operation-api.mdx b/docs/cloud/operation-api.mdx index 498f2a1606..3c1cc084de 100644 --- a/docs/cloud/operation-api.mdx +++ b/docs/cloud/operation-api.mdx @@ -12,11 +12,9 @@ tags: - Temporal Cloud --- -:::tip Support, stability, and dependency info +import { ReleaseStage } from '@site/src/components'; -The Temporal Cloud Operations API is in [Public Preview](/evaluate/development-production-features/release-stages#public-preview). - -::: + The Temporal Cloud Operations API, or the Cloud Ops API, is an open source, public [HTTP API](https://saas-api.tmprl.cloud/docs/httpapi.html#description/introduction) and [gRPC API](https://github.com/temporalio/cloud-api/tree/main) for programmatically managing Temporal Cloud control plane resources, including [Namespaces](/cloud/namespaces), [Users](/cloud/users), [Service Accounts](/cloud/service-accounts), [API keys](/cloud/api-keys), and others. The Temporal Cloud [Terraform Provider](/cloud/terraform-provider), [tcld CLI](/cloud/tcld), and Web UI all use the Cloud Ops API. diff --git a/docs/cloud/worker-health.mdx b/docs/cloud/worker-health.mdx index 2470ee2853..335b2cb69d 100644 --- a/docs/cloud/worker-health.mdx +++ b/docs/cloud/worker-health.mdx @@ -26,6 +26,9 @@ keywords: - workflow task execution size - temporal worker resources --- + +import { ReleaseStage } from '@site/src/components'; + import { LANGUAGE_TAB_GROUP, getLanguageLabel } from '@site/src/constants/languageTabs'; import SdkTabs from '@site/src/components'; import Tabs from '@theme/Tabs'; @@ -367,11 +370,7 @@ rate(temporal_sticky_cache_total_forced_eviction_total{namespace="$namespace"}[5 ## Manage Worker Heartbeating {#manage-worker-heartbeating} -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -This feature is currently in [Public Preview](/evaluate/development-production-features/release-stages#public-preview). - -::: + Workers send a heartbeat to Temporal Server every 60 seconds by default. This heartbeat serves to provide liveness and configuration data from the Worker to the Server. Specific data sent can be found in the [API](https://github.com/temporalio/api/blob/master/temporal/api/worker/v1/message.proto). By providing a consistent heartbeat from diff --git a/docs/develop/dotnet/nexus/feature-guide.mdx b/docs/develop/dotnet/nexus/feature-guide.mdx index eb2b4b19e8..63e4a08a6d 100644 --- a/docs/develop/dotnet/nexus/feature-guide.mdx +++ b/docs/develop/dotnet/nexus/feature-guide.mdx @@ -14,15 +14,9 @@ tags: - .NET SDK --- -import { CaptionedImage } from '@site/src/components'; +import { CaptionedImage, ReleaseStage } from '@site/src/components'; -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal .NET SDK support for Nexus is at [Pre-release](/evaluate/development-production-features/release-stages#pre-release). - -All APIs are experimental and may be subject to backwards-incompatible changes. - -::: + Use [Temporal Nexus](/evaluate/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. diff --git a/docs/develop/go/nexus/feature-guide.mdx b/docs/develop/go/nexus/feature-guide.mdx index 2524df3704..1d608f1ab7 100644 --- a/docs/develop/go/nexus/feature-guide.mdx +++ b/docs/develop/go/nexus/feature-guide.mdx @@ -18,12 +18,6 @@ tags: import { CaptionedImage } from '@site/src/components'; -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal Go SDK support for Nexus is now [Generally Available](/evaluate/development-production-features/release-stages#general-availability). - -::: - Use [Temporal Nexus](/evaluate/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. This page shows how to do the following: diff --git a/docs/develop/java/nexus/feature-guide.mdx b/docs/develop/java/nexus/feature-guide.mdx index bb3fd96a08..1abaa58c50 100644 --- a/docs/develop/java/nexus/feature-guide.mdx +++ b/docs/develop/java/nexus/feature-guide.mdx @@ -17,13 +17,6 @@ tags: import { CaptionedImage } from '@site/src/components'; -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal Java SDK support for Nexus is now -[Generally Available](/evaluate/development-production-features/release-stages#general-availability). - -::: - Use [Temporal Nexus](/evaluate/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. diff --git a/docs/develop/python/nexus/feature-guide.mdx b/docs/develop/python/nexus/feature-guide.mdx index 573b28869c..aaf9e5bd23 100644 --- a/docs/develop/python/nexus/feature-guide.mdx +++ b/docs/develop/python/nexus/feature-guide.mdx @@ -17,12 +17,6 @@ tags: import { CaptionedImage } from '@site/src/components'; -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal Python SDK support for Nexus is now [Generally Available](/evaluate/development-production-features/release-stages#general-availability). - -::: - Use [Temporal Nexus](/evaluate/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. This page shows how to do the following: @@ -105,17 +99,14 @@ from dataclasses import dataclass import nexusrpc - @dataclass class MyInput: name: str - @dataclass class MyOutput: message: str - @nexusrpc.service class MyNexusService: my_sync_operation: nexusrpc.Operation[MyInput, MyOutput] @@ -152,7 +143,6 @@ class MyNexusServiceHandler: return MyOutput(message=f"Hello {input.name} from sync operation!") ``` - A synchronous operation handler must return quickly (less than `10s`). Implementations can also make other calls, but handlers should be reliable to avoid tripping the [circuit breaker](/nexus/operations#circuit-breaking). @@ -184,7 +174,6 @@ class GreetingServiceHandler: In addition to `nexus.client()`, you can use `nexus.info()` to access information about the currently-executing Nexus Operation including its Task Queue. - ### Develop an Asynchronous Nexus Operation handler to start a Workflow Use the `@nexus.workflow_run_operation` decorator, which is the easiest way to expose a Workflow as an operation. @@ -248,11 +237,9 @@ class MyNexusServiceHandler: id=str(uuid.uuid4()), ) - ``` - ### Register your Nexus Service handler in a Worker After developing an asynchronous Nexus Operation handler to start a Workflow, the next step is to register your Nexus Service handler in a Worker. diff --git a/docs/develop/typescript/nexus/feature-guide.mdx b/docs/develop/typescript/nexus/feature-guide.mdx index bf38b8288e..0f8adf2aba 100644 --- a/docs/develop/typescript/nexus/feature-guide.mdx +++ b/docs/develop/typescript/nexus/feature-guide.mdx @@ -14,15 +14,9 @@ tags: - TypeScript SDK --- -import { CaptionedImage } from "@site/src/components"; +import { CaptionedImage, ReleaseStage } from '@site/src/components'; -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal TypeScript SDK support for Nexus is at [Pre-release](/evaluate/development-production-features/release-stages#pre-release). - -All APIs are experimental and may be subject to backwards-incompatible changes. - -::: + Use [Temporal Nexus](/evaluate/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. diff --git a/docs/develop/worker-performance.mdx b/docs/develop/worker-performance.mdx index 26f605e98b..a9e4ee6d17 100644 --- a/docs/develop/worker-performance.mdx +++ b/docs/develop/worker-performance.mdx @@ -9,7 +9,7 @@ tags: - Performance --- -import { CaptionedImage } from '@site/src/components'; +import { CaptionedImage, ReleaseStage } from '@site/src/components'; import { LANGUAGE_TAB_GROUP, getLanguageLabel } from '@site/src/constants/languageTabs'; import SdkTabs from '@site/src/components'; @@ -124,12 +124,12 @@ If it does, it may try to reserve an Activity Slot for the execution of the Acti #### Eager Workflow Start -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO + Eager Workflow Start is available in [Public Preview](/evaluate/development-production-features/release-stages#public-preview) in the Go, Java, Python, and .NET SDKs. Eager Workflow Start is enabled for all Temporal Cloud users and self-hosted Temporal Server 1.29.0+. No additional configuration or access request is needed. However, you must set Request-Eager-Start to true when starting each Workflow for Eager Workflow Start to be used. -::: + Eager Workflow Start reduces the latency required to initiate a Workflow execution. It is recommended for short-lived Workflows that use Local Activities to interact with external services, especially when these interactions are initiated in the first Workflow Task and the Workflow is deployed near the Temporal Server to minimize network delay. diff --git a/docs/encyclopedia/nexus/nexus-metrics.mdx b/docs/encyclopedia/nexus/nexus-metrics.mdx index fbc8b38f40..ea27de5249 100644 --- a/docs/encyclopedia/nexus/nexus-metrics.mdx +++ b/docs/encyclopedia/nexus/nexus-metrics.mdx @@ -17,13 +17,6 @@ keywords: - nexus oss metrics --- -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal Nexus is now [Generally Available](/evaluate/development-production-features/release-stages#general-availability) for [Temporal Cloud](/cloud/nexus) and [self-hosted deployments](/production-deployment/self-hosted-guide/nexus). - -::: - - Nexus provides SDK metrics, Cloud metrics, and OSS Cluster metrics in addition to integrated [execution debugging](/nexus/execution-debugging). ## SDK Metrics diff --git a/docs/evaluate/development-production-features/temporal-nexus.mdx b/docs/evaluate/development-production-features/temporal-nexus.mdx index 08b2041c4f..545cf2384d 100644 --- a/docs/evaluate/development-production-features/temporal-nexus.mdx +++ b/docs/evaluate/development-production-features/temporal-nexus.mdx @@ -34,12 +34,6 @@ keywords: import { RelatedReadContainer, RelatedReadItem } from '@site/src/components'; import ThemedImage from '@theme/ThemedImage'; -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal Nexus is now [Generally Available](/evaluate/development-production-features/release-stages#general-availability) for [Temporal Cloud](/cloud/nexus) and [self-hosted deployments](/production-deployment/self-hosted-guide/nexus). - -::: - As Temporal adoption grows across teams, organizations partition their applications into isolated Namespaces for security and fault isolation. Nexus bridges these boundaries, connecting Temporal applications across Namespaces, regions, and clouds with built-in durable execution, observability, and access control. Each team retains ownership of their own Namespace while sharing capabilities through clean service contracts. diff --git a/docs/evaluate/temporal-cloud/pricing.mdx b/docs/evaluate/temporal-cloud/pricing.mdx index 8b1c4e3ede..72828a5f73 100644 --- a/docs/evaluate/temporal-cloud/pricing.mdx +++ b/docs/evaluate/temporal-cloud/pricing.mdx @@ -21,7 +21,7 @@ tags: - Support --- -import { DiscoverableDisclosure } from '@site/src/components'; +import { DiscoverableDisclosure, ReleaseStage } from '@site/src/components'; Temporal Cloud is a consumption-based service. You pay only for what you use. @@ -44,7 +44,6 @@ Your total invoice each calendar month is the combination of Temporal Cloud cons **How plans work** - Each Temporal Cloud account includes a plan with Support, Actions, Active Storage, Retained Storage and platform features. Base allocations help you get started with the Temporal platform, so you can better estimate costs. @@ -269,11 +268,7 @@ On-Demand capacity is automatically adjusted based on past usage. Provisioned Capacity modes lets you define the capacity that is needed by your Workflow and is useful to handle traffic outside of the standard on-demand limits. See details on how capacity is set and the associated limits at [Capacity Modes](/cloud/capacity-modes). -:::tip Support, stability, and dependency info - -Provisioned Capacity is currently in [Public Preview](/evaluate/development-production-features/release-stages#public-preview). - -::: + **How does pricing for Capacity Modes work?** @@ -309,8 +304,6 @@ Temporal’s approach to pricing Provisioned Capacity aligns with our goal to on The minimum hourly allocation will have no impact on your price if you utilize the requested capacity above your default by 20% or more, and will only incur an additional charge if the requested capacity is not used. To avoid being charged for provisioned capacity it is advised to "return" capacity to the pool and switch back to the On-demand mode when usage is stable. - - ### High Availability feature pricing {#high-availability-features} **How does the pricing for High Availability (HA) features work?** diff --git a/docs/evaluate/temporal-cloud/service-availability.mdx b/docs/evaluate/temporal-cloud/service-availability.mdx index ee69dd3676..579a24e4a2 100644 --- a/docs/evaluate/temporal-cloud/service-availability.mdx +++ b/docs/evaluate/temporal-cloud/service-availability.mdx @@ -14,6 +14,8 @@ tags: - Temporal Cloud --- +import { ReleaseStage } from '@site/src/components'; + The operating envelope of Temporal Cloud includes throughput, latency, and limits. Service regions are listed on [this page](/cloud/regions). If you need more details, [contact us](https://pages.temporal.io/contact-us). @@ -27,11 +29,7 @@ Temporal offers two different modes for adjusting capacity: On-Demand Capacity o With On-Demand Capacity, Namespace capacity is increased automatically along with usage. With Provisioned Capacity, you can control your capacity limits by requesting Temporal Resource Units (TRUs). -:::tip Support, stability, and dependency info - -Provisioned Capacity is currently in [Public Preview](/evaluate/development-production-features/release-stages#public-preview). - -::: + ## Latency Service Level Objective (SLO) {#latency} diff --git a/docs/production-deployment/self-hosted-guide/temporal-nexus.mdx b/docs/production-deployment/self-hosted-guide/temporal-nexus.mdx index b59ece929a..95e78a2e14 100644 --- a/docs/production-deployment/self-hosted-guide/temporal-nexus.mdx +++ b/docs/production-deployment/self-hosted-guide/temporal-nexus.mdx @@ -11,12 +11,6 @@ tags: - enable-nexus --- -:::tip SUPPORT, STABILITY, and DEPENDENCY INFO - -Temporal Nexus is now [Generally Available](/evaluate/development-production-features/release-stages#general-availability). - -::: - :::info NEW TO NEXUS? This page explains how to self-host Nexus. To learn about Nexus, see the [how Nexus works page](/nexus). To evaluate whether Nexus fits your use case, see the [evaluation guide](/evaluate/nexus). diff --git a/src/components/index.js b/src/components/index.js index 07b4ad9ef6..a0f6296621 100644 --- a/src/components/index.js +++ b/src/components/index.js @@ -17,6 +17,7 @@ export { default as ZoomingImage } from './images/ZoomingImage'; // Information components export { default as DiscoverableDisclosure } from './info/DiscoverableDisclosure'; +export { default as ReleaseStage } from './info/ReleaseStage'; export { default as ToolTipTerm } from './info/ToolTipTerm'; export { RelatedReadContainer, RelatedReadItem } from './info/RelatedRead'; export { default as RelatedReadList } from './info/RelatedReadList'; diff --git a/src/components/info/ReleaseStage.js b/src/components/info/ReleaseStage.js new file mode 100644 index 0000000000..3ac3f6ae7e --- /dev/null +++ b/src/components/info/ReleaseStage.js @@ -0,0 +1,56 @@ +import React from "react"; +import Admonition from "@theme/Admonition"; +import Link from "@docusaurus/Link"; + +const STAGE_CONFIG = { + "pre-release": { + label: "Pre-release", + anchor: "#pre-release", + }, + "public-preview": { + label: "Public Preview", + anchor: "#public-preview", + }, +}; + +const RELEASE_STAGES_PATH = "/evaluate/development-production-features/release-stages"; + +/** + * ReleaseStage - Standardized release phase callout. + * + * Usage: + * + * + * + * All APIs are experimental and may be subject to backwards-incompatible changes. + * + * + * Custom content with multiple stages or non-standard text. + * + */ +export default function ReleaseStage({ stage, feature, verb = "is", children }) { + const config = stage ? STAGE_CONFIG[stage] : null; + + if (config && feature) { + return ( + +

+ {feature} {verb} in{" "} + {config.label}. +

+ {children} + + ); + } + + // Children-only mode for complex/multi-stage callouts + return ( + + {children} + + ); +}