From c659e9ec15d6cdbb2dca9723bedc54100c50fe67 Mon Sep 17 00:00:00 2001 From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> Date: Tue, 27 May 2025 11:01:31 -0400 Subject: [PATCH] docs: Update TS documentation for GA (#5761) --- website/content/docs/api-clients/client-agent.mdx | 2 -- .../docs/concepts/connection-workflows/index.mdx | 2 -- .../content/docs/concepts/transparent-sessions.mdx | 6 ++---- .../target-aliases/transparent-sessions.mdx | 4 +--- .../docs/install-boundary/install-clients.mdx | 14 ++++---------- website/data/docs-nav-data.json | 6 +++--- 6 files changed, 10 insertions(+), 24 deletions(-) diff --git a/website/content/docs/api-clients/client-agent.mdx b/website/content/docs/api-clients/client-agent.mdx index 2beadecee7..488502a4c1 100644 --- a/website/content/docs/api-clients/client-agent.mdx +++ b/website/content/docs/api-clients/client-agent.mdx @@ -9,8 +9,6 @@ description: >- @include 'alerts/enterprise-only.mdx' -@include 'alerts/beta.mdx' - The Boundary Client Agent is Boundary's DNS daemon. When the Boundary Client Agent runs alongside an authenticated Boundary client, the agent establishes itself as the primary resolver on the system and intercepts DNS requests. diff --git a/website/content/docs/concepts/connection-workflows/index.mdx b/website/content/docs/concepts/connection-workflows/index.mdx index fae371eef5..e3adf7f9dc 100644 --- a/website/content/docs/concepts/connection-workflows/index.mdx +++ b/website/content/docs/concepts/connection-workflows/index.mdx @@ -21,8 +21,6 @@ To practice using the `boundary connect` command in a development environment, r @include 'alerts/enterprise-only.mdx' -@include 'alerts/beta.mdx' - Transparent sessions shift Boundary from an active connection model to a passive connection model. Instead of interacting with the Boundary CLI or Desktop client and having to remember specific IDs or ephemeral ports to connect to targets, Boundary operates in the background. If a user is authenticated and authorized, Boundary intercepts DNS calls and routes traffic through a session automatically. diff --git a/website/content/docs/concepts/transparent-sessions.mdx b/website/content/docs/concepts/transparent-sessions.mdx index 7c8a827965..572c4c7584 100644 --- a/website/content/docs/concepts/transparent-sessions.mdx +++ b/website/content/docs/concepts/transparent-sessions.mdx @@ -9,8 +9,6 @@ description: >- @include 'alerts/enterprise-only.mdx' -@include 'alerts/beta.mdx' - Transparent sessions shift Boundary from an active connection model to a passive connection model. Boundary operates in the background instead of requiring you to remember specific resource IDs or ephemeral ports to connect to targets. As long as Boundary authenticates a user and the user is authorized to access the target, Boundary intercepts the DNS call and routes traffic through a session automatically. @@ -19,13 +17,13 @@ Transparent sessions require [aliases](/boundary/docs/concepts/aliases) and the The Boundary Desktop client facilitates quick target discovery and session establishment using your preferred client. If you configure aliases for your targets, install the Boundary Client Agent, and ensure you are authenticated to the cluster, connections are transparent to the user. Boundary provides OS notifications to make it clear when you connect to a target using a transparent session. -Boundary supports Windows and MacOS for the transparent sessions public beta. +Boundary supports Windows and MacOS for transparent sessions. Refer to the [Configure transparent sessions](/boundary/docs/configuration/target-aliases/transparent-sessions) page to get started. ## Known issues -Refer to the following table for known issues that may affect the public beta: +Refer to the following table for known issues: | Issue | Description | | ----- | ----------- | diff --git a/website/content/docs/configuration/target-aliases/transparent-sessions.mdx b/website/content/docs/configuration/target-aliases/transparent-sessions.mdx index 7e0eeaa99f..116c19819e 100644 --- a/website/content/docs/configuration/target-aliases/transparent-sessions.mdx +++ b/website/content/docs/configuration/target-aliases/transparent-sessions.mdx @@ -9,8 +9,6 @@ description: >- @include 'alerts/enterprise-only.mdx' -@include 'alerts/beta.mdx' - ## Requirements Before you configure transparent sessions, you must: @@ -55,7 +53,7 @@ Make sure to select the options **Boundary Client Agent**, **CLI**, and **Deskto ## Configure targets -The following section details how to configure targets and test the transparent sessions public beta feature. +The following section details how to configure targets and use transparent sessions. diff --git a/website/content/docs/install-boundary/install-clients.mdx b/website/content/docs/install-boundary/install-clients.mdx index c84076a36f..0dc4385a6b 100644 --- a/website/content/docs/install-boundary/install-clients.mdx +++ b/website/content/docs/install-boundary/install-clients.mdx @@ -21,17 +21,11 @@ correct clients: @include 'alerts/enterprise-only.mdx' - - - The Boundary installer includes the Boundary Client Agent, which is a beta feature. For production environments, consider downloading the Boundary binary and Boundary Desktop Client directly from the [Install Boundary](/boundary/install) page. - - - The Boundary installer bundles together the following components: - Boundary binary (CLI) - Boundary Desktop Client app -- Boundary Client Agent HCP/ENT BETA +- Boundary Client Agent HCP/ENT Download the appropriate Boundary installer for your Windows, MacOS, or Linux environment from the [Install Boundary](/boundary/install#installer) page or the [releases](https://releases.hashicorp.com/boundary-installer) page. You can also download the components individually, but compatibility is not guaranteed. Refer to the [Supported versions policy](/boundary/docs/enterprise/supported-versions#control-plane-and-client-cli-compatibility) to learn more. @@ -41,7 +35,7 @@ Download the appropriate Boundary installer for your Windows, MacOS, or Linux en -To learn more about installing the Boundary CLI and Boundary Desktop Client app, refer to the [Get started with HCP Boundary](/boundary/tutorials/get-started-hcp) tutorials. +To learn more about installing the Boundary CLI and Boundary Desktop Client app, refer to the [Get started with HCP Boundary](/boundary/tutorials/get-started-hcp) tutorials. @@ -51,7 +45,7 @@ We recommend the following components for end users: - Boundary binary (CLI) - Boundary Desktop Client app -Download these components for your Windows, MacOS, or Linux environment from the [Install Boundary](/boundary/install) page or the [HashiCorp releases](https://releases.hashicorp.com/) page. +Download these components for your Windows, MacOS, or Linux environment from the [Install Boundary](/boundary/install) page or the [HashiCorp releases](https://releases.hashicorp.com/) page. @@ -59,7 +53,7 @@ Client compatibility is not guaranteed. You should always ensure that your clien -To learn more about installing the Boundary CLI and Boundary Desktop Client app, refer to the [Get started with self-managed Boundary](/boundary/tutorials/get-started-community) tutorials. +To learn more about installing the Boundary CLI and Boundary Desktop Client app, refer to the [Get started with self-managed Boundary](/boundary/tutorials/get-started-community) tutorials. \ No newline at end of file diff --git a/website/data/docs-nav-data.json b/website/data/docs-nav-data.json index 1fd3d8050e..6ed5b430ff 100644 --- a/website/data/docs-nav-data.json +++ b/website/data/docs-nav-data.json @@ -202,7 +202,7 @@ { "title": "Transparent sessions", "badge": { - "text": "HCP/ENT BETA", + "text": "HCP/ENT", "type": "outlined", "color": "neutral" }, @@ -609,7 +609,7 @@ { "title": "Connect using transparent sessions", "badge": { - "text": "HCP/ENT BETA", + "text": "HCP/ENT", "type": "outlined", "color": "neutral" }, @@ -1689,7 +1689,7 @@ { "title": "Client Agent", "badge": { - "text": "HCP/ENT BETA", + "text": "HCP/ENT", "type": "outlined", "color": "neutral" },