feat: new changelog (#149)

Author: insider89

docs/launch-platform/self-hosted/installation-guide/prerequisites/overview.md

@@ -77,11 +77,11 @@ Make sure to complete **all** prerequisites before proceeding with the platform
 - Blockchain data persistence
 - [Setup Guide](/documentation/docs/launch-platform/self-hosted/installation-guide/prerequisites/s3-compatible-storage)
 
-#### HashiCorp Vault
+#### Secrets management
 
 - Secrets management
 - Encryption keys
-- [Setup Guide](/documentation/docs/launch-platform/self-hosted/installation-guide/prerequisites/hashicorp-vault)
+- [Setup Guide](/documentation/docs/launch-platform/self-hosted/installation-guide/prerequisites/secret-management)
 
 #### OAuth Provider
 

docs/launch-platform/self-hosted/installation-guide/prerequisites/redis.md

@@ -24,6 +24,18 @@ Redis serves as a critical component for:
 
 ### Cloud Provider Options
 
+#### Google Cloud Memorystore
+
+1. **Enable and Configure**
+   - Go to [Google Cloud Console](https://console.cloud.google.com)
+   - Enable Memorystore for Redis API
+   - Create new Redis instance:
+     - Choose Basic tier for standard workloads
+     - Select region (same as your GKE cluster)
+     - Set memory capacity (minimum 1GB)
+     - Enable authentication (recommended)
+   - Configure VPC network and authorized networks
+
 #### Redis Cloud
 
 1. Create account at [Redis Cloud](https://app.redislabs.com)
@@ -124,19 +136,32 @@ For production use:
 
 - [ ] Redis hostname/endpoint
 - [ ] Port number (default: 6379)
-- [ ] Password
+- [ ] Password (if authentication enabled)
 - [ ] TLS enabled/disabled
 
-:::note Example Configuration
-
+:::note Example Helm Values
 ```yaml
+# values.yaml
 redis:
-  host: 'your-redis-host'
+  # -- The redis host you collected in the prerequisites
+  host: ''
+  # -- The redis port you collected in the prerequisites
   port: 6379
-  password: 'your-secure-password'
-  tls: true # Set to false for local development
+  # -- The redis password you collected in the prerequisites
+  password: ''
+  # -- In shared redis servers, this prefix will separate out all queues
+  prefix: 'sm'
+  # -- Set to true if you want to use the TLS mode
+  tls: false
+
 ```
+:::
 
+:::tip
+When using Google Memorystore:
+1. Enable only one Redis solution (`redis.enabled` or `redis.memorystore.enabled`)
+2. Ensure your GKE cluster has access to the Memorystore instance
+3. Configure the same region as your GKE cluster
 :::
 
 </div>
@@ -145,6 +170,23 @@ redis:
 
 Test your Redis connection:
 
+<Tabs>
+<TabItem value="memorystore" label="Google Memorystore">
+
+```bash
+# Get the Memorystore instance connection details
+REDIS_HOST=$(gcloud redis instances describe [INSTANCE_ID] \
+    --region=[REGION] --format='get(host)')
+REDIS_PORT=$(gcloud redis instances describe [INSTANCE_ID] \
+    --region=[REGION] --format='get(port)')
+
+# Test connection using redis-cli
+redis-cli -h $REDIS_HOST -p $REDIS_PORT ping
+```
+
+</TabItem>
+<TabItem value="standard" label="Standard Redis">
+
 ```bash
 # Using redis-cli
 redis-cli -h your-redis-host -p 6379 -a your-password ping
@@ -153,22 +195,26 @@ redis-cli -h your-redis-host -p 6379 -a your-password ping
 PONG
 ```
 
+</TabItem>
+</Tabs>
+
 ## Troubleshooting
 
 Common issues and solutions:
 
 1. **Connection Failures**
-
    - Verify credentials
    - Check network/firewall rules
    - Confirm TLS settings
    - Validate endpoint format
+   - For Memorystore: verify VPC peering
 
 2. **Performance Issues**
    - Monitor memory usage
    - Check eviction policies
    - Review connection limits
    - Verify resource allocation
+   - For Memorystore: check instance tier
 
 ## Next Steps
 

docs/launch-platform/self-hosted/installation-guide/prerequisites/s3-compatible-storage.md

@@ -338,7 +338,7 @@ Common issues and solutions:
 
 1. ✅ Set up S3-compatible storage
 2. ✅ Generate encryption key
-3. ➡️ Proceed to [HashiCorp Vault Setup](/documentation/docs/launch-platform/self-hosted/installation-guide/prerequisites/hashicorp-vault)
+3. ➡️ Proceed to [Secret Management Setup](/documentation/docs/launch-platform/self-hosted/installation-guide/prerequisites/secret-management)
 
 :::tip Need Help?
 Contact [support@settlemint.com](mailto:support@settlemint.com) if you encounter any issues.

…n-guide/prerequisites/hashicorp-vault.md …guide/prerequisites/secret-management.mddocs/launch-platform/self-hosted/installation-guide/prerequisites/hashicorp-vault.md renamed to docs/launch-platform/self-hosted/installation-guide/prerequisites/secret-management.md docs/launch-platform/self-hosted/installation-guide/prerequisites/hashicorp-vault.md renamed to docs/launch-platform/self-hosted/installation-guide/prerequisites/secret-management.md

@@ -1,17 +1,20 @@
 ---
-title: HashiCorp Vault
+title: Secret Management
 sidebar_position: 7
 ---
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-# HashiCorp Vault Setup
+# Secret Management Setup
 
 ## Overview
 
-HashiCorp Vault is used for:
+Our platform supports two options for secret management:
+- HashiCorp Vault
+- Google Secret Manager
 
+Both services are used for:
 - Secrets management
 - Encryption key storage
 - Secure credentials handling
@@ -20,7 +23,59 @@ HashiCorp Vault is used for:
 ## Deployment Options
 
 <Tabs>
-<TabItem value="cloud" label="HCP Vault (Recommended)" default>
+<TabItem value="gsm" label="Google Secret Manager" default>
+
+### Google Secret Manager Setup
+
+1. **Enable the Secret Manager API**
+   - Go to [Google Cloud Console](https://console.cloud.google.com)
+   - Navigate to Secret Manager
+   - Enable the Secret Manager API for your project
+
+2. **Create Service Account**
+   - Navigate to IAM & Admin > Service Accounts
+   - Create a new service account
+   - Grant the following roles:
+     - `Secret Manager Admin`
+
+3. **Download Credentials**
+   - Create and download a JSON key for the service account
+   - Keep this file secure - you'll need it during platform installation
+
+:::tip
+Google Secret Manager provides:
+- Fully managed service
+- Automatic replication
+- Fine-grained IAM controls
+- Audit logging
+:::
+
+**Helm Chart Values:**
+```yaml
+# values.yaml for Helm installation
+googleSecretManager:
+  # -- Enable Google Secret Manager integration
+  enabled: true
+  # -- The Google Cloud project ID
+  projectId: "your-project-id"
+  # -- The Google Cloud service account credentials JSON
+  credentials: |
+    {
+      // Your service account JSON key
+    }
+```
+:::
+
+:::tip
+Make sure to:
+1. Enable Google Secret Manager in your Helm values
+2. Use the same project ID and credentials as in your platform configuration
+3. Properly format the service account JSON credentials
+:::
+
+</TabItem>
+
+<TabItem value="hcp" label="HCP Vault" default>
 
 ### HashiCorp Cloud Platform Setup
 
@@ -100,7 +155,8 @@ HCP Vault provides:
   :::
 
 </TabItem>
-<TabItem value="helm" label="Self-Hosted">
+
+<TabItem value="self-hosted" label="Self-Hosted Vault">
 
 ### Helm Chart Installation
 
@@ -146,27 +202,85 @@ For production:
 
 ### Required Values for Platform Installation
 
+Choose one of the following configurations for your Helm values:
+
+**For Google Secret Manager:**
+- [ ] GCP Project ID
+- [ ] Service Account JSON key
+
+:::note Example Helm Values for GSM
+```yaml
+# values.yaml
+vault:
+  enabled: false
+
+googleSecretManager:
+  # -- Enable Google Secret Manager integration
+  enabled: true
+  # -- The Google Cloud project ID
+  projectId: 'your-project-id'
+  # -- The Google Cloud service account credentials JSON
+  credentials: |
+    {
+      // Your service account JSON key
+    }
+```
+:::
+
+**For HashiCorp Vault:**
 - [ ] Vault address/endpoint
 - [ ] Role ID
 - [ ] Secret ID
 - [ ] Namespace (if using HCP Vault: `admin`)
 
-:::note Example Configuration
-
+:::note Example Helm Values for Vault
 ```yaml
+# values.yaml
+googleSecretManager:
+  enabled: false
+
 vault:
+  # -- Enable Hashicorp Vault integration
+  enabled: true
+  # -- The vault address you collected in the prerequisites
   address: 'https://vault-cluster.hashicorp.cloud:8200'
-  namespace: 'admin' # Required for HCP Vault
+  # -- The vault namespace you collected in the prerequisites
+  namespace: 'admin'  # Required for HCP Vault
+  # -- The AppRole roleId you collected in the prerequisites
   roleId: 'your-role-id'
+  # -- The AppRole secretId you collected in the prerequisites
   secretId: 'your-secret-id'
 ```
+:::
 
+:::important
+Make sure to:
+1. Enable only one secret management solution (`vault` or `googleSecretManager`)
+2. Disable the other option by setting `enabled: false`
+3. Provide all required values for your chosen solution
 :::
 
 </div>
 
 ## Validation
 
+Test your secret management configuration:
+
+<Tabs>
+<TabItem value="gsm" label="Google Secret Manager">
+
+```bash
+# Set environment variables
+export GOOGLE_APPLICATION_CREDENTIALS="path/to/service-account.json"
+export PROJECT_ID="your-project-id"
+
+# Verify access
+gcloud secrets list --project=$PROJECT_ID
+```
+
+</TabItem>
+<TabItem value="vault" label="HashiCorp Vault">
+
 Test your Vault configuration:
 
 ```bash
@@ -182,26 +296,28 @@ vault write auth/approle/login \
   secret_id=$VAULT_SECRET_ID
 ```
 
+</TabItem>
+</Tabs>
+
 ## Troubleshooting
 
 Common issues and solutions:
 
-1. **Authentication Failures**
-
-   - Verify role ID and secret ID
-   - Check policy attachments
-   - Confirm namespace setting
-   - Validate token TTLs
+1. **Google Secret Manager Issues**
+   - Verify service account permissions
+   - Check credentials file format
+   - Confirm API is enabled
+   - Validate project ID
 
-2. **Connection Issues**
+2. **Vault Issues**
    - Verify Vault address
    - Check network access
    - Confirm TLS settings
    - Validate namespace (HCP)
 
 ## Next Steps
 
-1. ✅ Set up Vault instance
+1. ✅ Set up secret management service
 2. ✅ Configure authentication
 3. ➡️ Proceed to [Metrics and Logs Setup](/documentation/docs/launch-platform/self-hosted/installation-guide/prerequisites/metrics-and-logs)