From ddb5098edaf24865f1120305056b0888e5acd88d Mon Sep 17 00:00:00 2001
From: x <x032205@gmail.com>
Date: Mon, 28 Apr 2025 19:09:13 -0400
Subject: [PATCH 1/3] only sync non-inherited environment variables

---
 .../secret-sync/teamcity/teamcity-sync-fns.ts      | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/backend/src/services/secret-sync/teamcity/teamcity-sync-fns.ts b/backend/src/services/secret-sync/teamcity/teamcity-sync-fns.ts
index 323f59851..6dbd9bdd7 100644
--- a/backend/src/services/secret-sync/teamcity/teamcity-sync-fns.ts
+++ b/backend/src/services/secret-sync/teamcity/teamcity-sync-fns.ts
@@ -10,7 +10,7 @@ import {
   TTeamCitySyncWithCredentials
 } from "@app/services/secret-sync/teamcity/teamcity-sync-types";
 
-// Note: Most variables won't be returned with a value due to them being a "password" type (starting with "env.").
+// Note: Most variables won't be returned with a value due to them being a "password" type.
 // TeamCity API returns empty string for password-type variables for security reasons.
 const listTeamCityVariables = async ({ instanceUrl, accessToken, project, buildConfig }: TTeamCityListVariables) => {
   const { data } = await request.get<TTeamCityListVariablesResponse>(
@@ -25,12 +25,16 @@ const listTeamCityVariables = async ({ instanceUrl, accessToken, project, buildC
     }
   );
 
+  // Filters for only non-inherited environment variables
   // Strips out "env." from map key, but the "name" field still has the original unaltered key.
   return Object.fromEntries(
-    data.property.map((variable) => [
-      variable.name.startsWith("env.") ? variable.name.substring(4) : variable.name,
-      { ...variable, value: variable.value || "" } // Password values will be empty strings from the API for security
-    ])
+    data.property
+      .filter((variable) => !variable.inherited)
+      .filter((variable) => variable.name.startsWith("env."))
+      .map((variable) => [
+        variable.name.substring(4),
+        { ...variable, value: variable.value || "" } // Password values will be empty strings from the API for security
+      ])
   );
 };
 

From 9f158d5b3fa81adcc8fdb4d3decbca26123290f9 Mon Sep 17 00:00:00 2001
From: x <x032205@gmail.com>
Date: Tue, 29 Apr 2025 10:35:56 -0400
Subject: [PATCH 2/3] feat(docs): Added note stating that inherited secrets are
 ignored

---
 docs/integrations/secret-syncs/teamcity.mdx | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/docs/integrations/secret-syncs/teamcity.mdx b/docs/integrations/secret-syncs/teamcity.mdx
index e79fc0f0c..932c98f8e 100644
--- a/docs/integrations/secret-syncs/teamcity.mdx
+++ b/docs/integrations/secret-syncs/teamcity.mdx
@@ -34,7 +34,11 @@ description: "Learn how to configure a TeamCity Sync for Infisical."
             - **Build Configuration**: The build configuration to sync secrets to.
 
             <Note>
-                Not including a Build Configuration will sync secrets to the entire project.
+                Not including a Build Configuration will sync secrets to the project.
+            </Note>
+
+            <Note>
+                Infisical only syncs secrets within the target scope, meaning that inherited secrets are ignored.
             </Note>
 
         5. Configure the **Sync Options** to specify how secrets should be synced, then click **Next**.

From 8e4ad8baf8c52639f9506a018b188ba1f9dc2425 Mon Sep 17 00:00:00 2001
From: x <x032205@gmail.com>
Date: Tue, 29 Apr 2025 12:43:44 -0400
Subject: [PATCH 3/3] docs tweak

---
 docs/integrations/secret-syncs/teamcity.mdx | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/docs/integrations/secret-syncs/teamcity.mdx b/docs/integrations/secret-syncs/teamcity.mdx
index 932c98f8e..af4c8d76a 100644
--- a/docs/integrations/secret-syncs/teamcity.mdx
+++ b/docs/integrations/secret-syncs/teamcity.mdx
@@ -37,10 +37,6 @@ description: "Learn how to configure a TeamCity Sync for Infisical."
                 Not including a Build Configuration will sync secrets to the project.
             </Note>
 
-            <Note>
-                Infisical only syncs secrets within the target scope, meaning that inherited secrets are ignored.
-            </Note>
-
         5. Configure the **Sync Options** to specify how secrets should be synced, then click **Next**.
         ![Configure Options](/images/secret-syncs/teamcity/teamcity-sync-options.png)
 
@@ -48,6 +44,11 @@ description: "Learn how to configure a TeamCity Sync for Infisical."
                 - **Overwrite Destination Secrets**: Removes any secrets at the destination endpoint not present in Infisical.
                 - **Import Secrets (Prioritize Infisical)**: Imports secrets from the destination endpoint before syncing, prioritizing values from Infisical over TeamCity when keys conflict.
                 - **Import Secrets (Prioritize TeamCity)**: Imports secrets from the destination endpoint before syncing, prioritizing values from TeamCity over Infisical when keys conflict.
+
+                <Note>
+                    Infisical only syncs secrets from within the target scope; inherited secrets will not be imported.
+                </Note>
+
             - **Auto-Sync Enabled**: If enabled, secrets will automatically be synced from the source location when changes occur. Disable to enforce manual syncing only.
             - **Disable Secret Deletion**: If enabled, Infisical will not remove secrets from the sync destination. Enable this option if you intend to manage some secrets manually outside of Infisical.