From 7b91e7192cac2d05d710153929b8074eb2fa956a Mon Sep 17 00:00:00 2001
From: Victor Santos <victor@infisical.com>
Date: Mon, 10 Nov 2025 16:43:06 -0300
Subject: [PATCH] Refactor secret path handling in InfisicalSecretInput to use
 folderPath directly, enhancing clarity in permission validation logic.

---
 .../v2/InfisicalSecretInput/InfisicalSecretInput.tsx        | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/frontend/src/components/v2/InfisicalSecretInput/InfisicalSecretInput.tsx b/frontend/src/components/v2/InfisicalSecretInput/InfisicalSecretInput.tsx
index d1f2e1a62..8da31d67d 100644
--- a/frontend/src/components/v2/InfisicalSecretInput/InfisicalSecretInput.tsx
+++ b/frontend/src/components/v2/InfisicalSecretInput/InfisicalSecretInput.tsx
@@ -387,8 +387,6 @@ export const InfisicalSecretInput = forwardRef<HTMLTextAreaElement, Props>(
           }
         }
 
-        const secretPath = segment === environmentSlug ? "/" : folderPath;
-
         // Only validate secret permission, users can always view environments and folders
         if (segment === secretName) {
           const canReadSecretValue = hasSecretReadValueOrDescribePermission(
@@ -396,8 +394,8 @@ export const InfisicalSecretInput = forwardRef<HTMLTextAreaElement, Props>(
             ProjectPermissionSecretActions.ReadValue,
             {
               environment: environmentSlug,
-              secretPath,
-              secretName: secretName ?? "*",
+              secretPath: folderPath,
+              secretName,
               secretTags: ["*"]
             }
           );