Describe the feature

Currently, our system relies on appsettings.json for configuration. To enhance security and flexibility, we want to integrate Infisical for managing secrets and configurations. Additionally, the system should support dynamic switching between appsettings.json and Infisical at runtime or via a configuration flag.

Acceptance Criteria

1. Infisical Integration

   • Implement secure access to Infisical secrets for all environments.
   • Support reading key-value pairs from Infisical as configuration values.
   • Ensure secrets are not logged or exposed in plain text.

2. Dynamic Configuration Source Switching

   • Allow the system to choose between appsettings.json and Infisical as the primary configuration source.
   • The selection should be configurable via environment variable or startup parameter.
   • Switching should not require code changes or recompilation.

3. Fallback Mechanism

   • If Infisical is unavailable, optionally fall back to appsettings.json with a warning log.

4. Security & Audit

   • Ensure access to Infisical secrets follows least privilege principles.
   • Log configuration source usage (appsettings.json or Infisical) without exposing sensitive values.

5. Documentation

   • Provide setup instructions for Infisical integration.
   • Document how to switch between configuration sources.

Optional Enhancements

• Support hot-reloading of secrets from Infisical without restarting the application.
• Provide unit tests to verify correct configuration source usage.