From d1bcbac5d14b3a0fcd31dd44072e13c423df135d Mon Sep 17 00:00:00 2001
From: Michael Li <michael.li@hashicorp.com>
Date: Tue, 18 Nov 2025 14:40:27 -0500
Subject: [PATCH] chore(e2e): Rename for clarity (#6261)

---
 .github/workflows/build.yml    | 4 ++--
 .github/workflows/enos-run.yml | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 137f8e2fe1..d6980f20cd 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -388,8 +388,8 @@ jobs:
             docker.io/hashicorppreview/${{ env.repo }}:${{ env.minor-version }}-dev
             docker.io/hashicorppreview/${{ env.repo }}:${{ env.minor-version }}-dev-${{ github.sha }}
 
-  enos:
-    name: Enos
+  e2e:
+    name: e2e
     # Only run the Enos workflow on pull requests that have been originated from
     # the hashicorp/boundary repository. As Enos scenarios require access to
     # Github Actions secrets, it only makes sense to run this workflow when those
diff --git a/.github/workflows/enos-run.yml b/.github/workflows/enos-run.yml
index a050a32a37..91d154c839 100644
--- a/.github/workflows/enos-run.yml
+++ b/.github/workflows/enos-run.yml
@@ -61,7 +61,7 @@ jobs:
           go mod download
           make tools
   enos:
-    name: Integration
+    name: test
     needs:
       - setup
     # Enos jobs are still a bit flaky, ensure they don't fail the workflow.