From 5eb9a1a667812f0d66b0b0feb5e7c20eb2a26c7b Mon Sep 17 00:00:00 2001
From: Scott Wilson <scottraywilson@gmail.com>
Date: Tue, 15 Apr 2025 15:07:39 -0700
Subject: [PATCH] improvement: add doc additions for single credential
 rotations

---
 .../platform/secret-rotation/overview.mdx      | 18 ++++++++++++++++++
 .../SecretRotationV2ConfigurationFields.tsx    | 13 +++++++++++--
 2 files changed, 29 insertions(+), 2 deletions(-)

diff --git a/docs/documentation/platform/secret-rotation/overview.mdx b/docs/documentation/platform/secret-rotation/overview.mdx
index ee1fd9e42..d11334440 100644
--- a/docs/documentation/platform/secret-rotation/overview.mdx
+++ b/docs/documentation/platform/secret-rotation/overview.mdx
@@ -47,6 +47,11 @@ Each set of credentials transitions through three distinct states:
 
 - **Active**: The primary credentials that will be used for new connections
 - **Inactive**: These credentials are still valid but are no longer issued for new connections
+    <Note>
+        Some rotation providers utilize a single credential set due to technical constraints. As a result, inactive credentials for these providers will immediately become invalid once rotated.
+
+        To avoid service interruptions, Infisical recommends manually rotating these credentials to prevent downtime.
+    </Note>
 - **Revoked**: Permanently invalidated and deleted from the system
 
 ### Rotation Cycle Example (30-Day Interval)
@@ -95,3 +100,16 @@ Using a __30-Day__ rotation interval as an example, here's how the process unfol
 
 - [PostgreSQL Credentials](./postgres)
 - [Microsoft SQL Server Credentials](./mssql)
+
+## FAQ
+
+<AccordionGroup>
+    <Accordion title="Why do certain rotations only use a single credential set?">
+        Some credential providers have limitations that affect rotation patterns:
+
+        - The third-party provider's API only supports managing one active credential set at a time
+        - The specific use-case (such as personal login accounts) is inherently limited to a single active credential
+
+        In either scenario, when service continuity is critical, Infisical recommends disabling auto-rotation and performing manual credential rotation during scheduled maintenance windows.
+    </Accordion>
+</AccordionGroup>
diff --git a/frontend/src/components/secret-rotations-v2/forms/SecretRotationV2ConfigurationFields.tsx b/frontend/src/components/secret-rotations-v2/forms/SecretRotationV2ConfigurationFields.tsx
index d96c8b3d2..1906b743d 100644
--- a/frontend/src/components/secret-rotations-v2/forms/SecretRotationV2ConfigurationFields.tsx
+++ b/frontend/src/components/secret-rotations-v2/forms/SecretRotationV2ConfigurationFields.tsx
@@ -126,11 +126,20 @@ export const SecretRotationV2ConfigurationFields = ({ isUpdate, environments }:
         }}
       />
       {!IS_ROTATION_DUAL_CREDENTIALS[type] && isAutoRotationEnabled && (
-        <div className="rounded border border-yellow bg-yellow/10 p-2 px-3 text-sm text-yellow">
+        <div className="rounded border border-yellow bg-yellow/10 p-2 px-3 text-xs text-yellow">
           <FontAwesomeIcon icon={faWarning} className="mr-1" /> Due to{" "}
           {SECRET_ROTATION_MAP[type].name} Rotations rotating a single credential set, auto-rotation
           may result in service interruptions. If you need to ensure service continuity, we
-          recommend disabling this option.
+          recommend disabling this option. <br />
+          <a
+            href="https://infisical.com/docs/documentation/platform/secret-rotation/overview#how-rotation-works"
+            target="_blank"
+            rel="noopener noreferrer"
+            className="underline decoration-yellow underline-offset-2 hover:text-mineshaft-200"
+          >
+            Read more
+          </a>
+          .
         </div>
       )}
     </>