feat: add secret management (#628)

Signed-off-by: Asish Kumar <[email protected]>

Author: officialasishkumar

versioned_docs/version-3.0.0/running-keploy/configuration-file.md

@@ -238,6 +238,28 @@ The tests section enables you to specify conditions for recording tests during A
 
 You can use the **`path`**, **`urlMethods`**, **`headers`**, and **`host`** filters together or independently based on your testing scenarios. This flexibility allows you to precisely define the conditions under which tests are recorded.
 
+### Managing Secrets with `secret.yaml`
+
+Keploy allows you to manage sensitive information like API keys or tokens securely, without hardcoding them into your test files. This is done using a `secret.yaml` file within each test set directory.
+
+1.  **Create `secret.yaml`**: Inside your test set directory (e.g., `keploy/test-set-0/`), create a file named `secret.yaml`.
+
+2.  **Define Your Secrets**: Add your secrets as key-value pairs.
+
+    ```yaml
+    Authorization: Bearer xyz.abc.123
+    ```
+
+3.  **Use Secrets in Tests**: Reference these values in your test cases or mocks using the `{{.secret.KEY}}` syntax.
+    `yaml
+    # inside a test-case.yaml
+    ...
+    header:
+        Authorization: '{{string .secret.Authorization }}'
+    ...
+    `
+    For your security, Keploy will automatically add `/*/secret.yaml` to your `.gitignore` file to prevent accidentally committing secrets.
+
 ### Bypass Rules Section
 
 The `bypassRules` section in the Keploy-config file allows you to define parameters for bypassing and mocking API calls.