backport of commit 5afc7fe

hashicorp · Nov 2, 2023 · 249ee92 · 249ee92
1 parent 85b7549
commit 249ee92
Show file tree

Hide file tree

Showing 8 changed files with 39 additions and 7 deletions.
diff --git a/website/content/docs/configuration/session-recording/create-storage-bucket.mdx b/website/content/docs/configuration/session-recording/create-storage-bucket.mdx
@@ -5,7 +5,7 @@ description: |-
   How to create a storage bucket for session recording in Boundary
 ---
 
-# Create a storage bucket
+# Create a storage bucket <sup>HCP/ENT</sup>
 
 As of Boundary 0.13.0, you can record and audit user sessions.
 A Boundary resource known as a [storage bucket](/boundary/docs/concepts/domain-model/storage-buckets) is used to store the recorded sessions.

diff --git a/website/content/docs/configuration/session-recording/enable-session-recording.mdx b/website/content/docs/configuration/session-recording/enable-session-recording.mdx
@@ -5,7 +5,7 @@ description: |-
   How to enable session recording on a target in Boundary
 ---
 
-# Enable session recording on a target
+# Enable session recording on a target <sup>HCP/ENT</sup>
 
 You must enable session recording for any targets that you want to record sessions on.
 When you [create a storage bucket](/boundary/docs/configuration/session-recording/create-storage-bucket), Boundary provides you with an ID.

diff --git a/website/content/docs/configuration/session-recording/index.mdx b/website/content/docs/configuration/session-recording/index.mdx
@@ -5,7 +5,7 @@ description: |-
   An overview of session recording in Boundary
 ---
 
-# Overview
+# Overview <sup>HCP/ENT</sup>
 
 Boundary provides auditing capabilities via session recording.
 In Boundary, a session represents a set of connections between a user and a host from a target.

diff --git a/website/content/docs/operations/session-recordings/index.mdx b/website/content/docs/operations/session-recordings/index.mdx
@@ -5,7 +5,9 @@ description: |-
   How to work with Boundary's recorded sessions
 ---
 
-# Recorded sessions operations
+# Recorded sessions operations <sup>HCP/ENT</sup>
+
+<EnterpriseAlert product="boundary" />
 
 Boundary provides [auditing](/boundary/docs/concepts/auditing) capabilities via [session recording](/boundary/docs/configuration/session-recording).
 In Boundary, a session represents a set of connections between a user and a host from a target.

diff --git a/website/content/docs/operations/session-recordings/manage-recorded-sessions.mdx b/website/content/docs/operations/session-recordings/manage-recorded-sessions.mdx
@@ -5,7 +5,7 @@ description: |-
   How to find, download, and view Boundary's recorded sessions
 ---
 
-# Find and view recorded sessions
+# Find and view recorded sessions <sup>HCP/ENT</sup>
 
 You can view a list of all recorded sessions, or if you know the ID of a specific recorded session, you can find any channels associated with that recording.
 

diff --git a/website/content/docs/operations/session-recordings/validate-data-store.mdx b/website/content/docs/operations/session-recordings/validate-data-store.mdx
@@ -4,7 +4,7 @@ page_title: Validate the data integrity in the external object store
 description: |-
   How Boundary validates the data integrity of recorded sessions in the external object store
 ---
-# How Boundary validates data integrity in the external object store
+# How Boundary validates data integrity in the external object store <sup>HCP/ENT</sup>
 
 When a Boundary worker uploads a BSR file to AWS S3 through the Boundary AWS plugin, the plugin calculates the SHA256 checksum of the contents of the BSR file and attaches this information to the object that is uploaded to S3.
 The SHA256 checksum value attached to the S3 object is returned to the Boundary worker.

diff --git a/website/content/docs/operations/session-recordings/validate-session-recordings.mdx b/website/content/docs/operations/session-recordings/validate-session-recordings.mdx
@@ -5,7 +5,7 @@ description: |-
   How to validate the integrity of Boundary's recorded sessions
 ---
 
-# Validate the integrity of session recordings
+# Validate the integrity of session recordings <sup>HCP/ENT</sup>
 
 BSR directories are validated based on the contents in the directory.
 Boundary cryptographically verifies each individual Boundary Session Recording (BSR) file.

diff --git a/website/data/docs-nav-data.json b/website/data/docs-nav-data.json
@@ -264,10 +264,20 @@
           },
           {
             "title": "Session recordings",
+            "badge": {
+              "text": "HCP/ENT",
+              "type": "outlined",
+              "color": "neutral"
+            },
             "path": "concepts/domain-model/session-recordings"
           },
           {
             "title": "Storage buckets",
+            "badge": {
+              "text": "HCP/ENT",
+              "type": "outlined",
+              "color": "neutral"
+            },
             "path": "concepts/domain-model/storage-buckets"
           },
           {
@@ -391,6 +401,11 @@
       },
       {
         "title": "Session recordings",
+        "badge": {
+          "text": "HCP/ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
         "routes": [
           {
             "title": "Overview",
@@ -454,6 +469,11 @@
       },
       {
         "title": "Session recordings",
+        "badge": {
+          "text": "HCP/ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
         "routes": [
           {
             "title": "Overview",
@@ -1084,6 +1104,11 @@
       },
       {
         "title": "session-recordings",
+        "badge": {
+          "text": "HCP/ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
         "routes": [
           {
             "title": "Overview",
@@ -1126,6 +1151,11 @@
       },
       {
         "title": "storage-buckets",
+        "badge": {
+          "text": "HCP/ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
         "routes": [
           {
             "title": "Overview",