From cb3d171d48d7b057cab41e5b9a263a878013dfff Mon Sep 17 00:00:00 2001 From: Scott Wilson Date: Mon, 3 Mar 2025 10:59:31 -0800 Subject: [PATCH] documentation: remove reference to secret affixes in secret syncs overview (temp) --- docs/integrations/secret-syncs/overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/secret-syncs/overview.mdx b/docs/integrations/secret-syncs/overview.mdx index bbe333efc..0df04cbb7 100644 --- a/docs/integrations/secret-syncs/overview.mdx +++ b/docs/integrations/secret-syncs/overview.mdx @@ -75,7 +75,7 @@ via the UI or API for the third-party service you intend to sync secrets to. 2. Create Secret Sync: Configure a Secret Sync in the desired project by specifying the following parameters via the UI or API: - Source: The project environment and folder path you wish to retrieve secrets from. - Destination: The App Connection to utilize and the destination endpoint to deploy secrets to. These can vary between services. - - Options: Customize how secrets should be synced. Examples include adding a suffix or prefix to your secrets, or importing secrets from the destination on the initial sync. + - Options: Customize how secrets should be synced, such as whether or not secrets should be imported from the destination on the initial sync. Secret Syncs are the source of truth for connected third-party services. Any secret,