Replace Hardcoded URLs/Paths with Environment Variables in Microservices

[AshhubAli]

This issue addresses the use of hardcoded URLs or paths within our microservices, aiming to replace them with environment variables stored in a configuration file (such as .env). By implementing this change, we aim to enhance flexibility, scalability, and maintainability across our microservices architecture.

Problem Statement:

1. Hardcoded URLs/Paths: Existing hardcoded URLs or paths in microservices lead to inflexibility and dependency, making deployment and scalability challenging.
2. Dependency on Static Configurations: Lack of flexibility due to reliance on static configurations embedded in the codebase hinders seamless deployment across different environments.

Key Objectives:

1. Migration to Environment Variables: Replace hardcoded URLs/paths with environment variables stored in a configuration file (e.g., .env) across relevant microservices.
2. Improved Flexibility and Portability: Enhance the agility of our microservices architecture by enabling dynamic configuration changes without code modifications.

Expected Outcomes:

• Reduced dependency on hardcoded configurations, enabling easier deployment and scalability.
• Enhanced flexibility to configure and adapt microservices across various environments (development, staging, production).
• Improved maintainability by centralizing configurations in a dedicated file (.env).

Additional Considerations:

• Documentation and guidelines for developers on setting up and managing environment variables in the configuration file.
• Testing and validation across different environments to ensure seamless functionality post-implementation.