bobbai00 opened a new issue, #3758: URL: https://github.com/apache/texera/issues/3758
## Description Currently, configuration values in `default.conf` are hardcoded and cannot be easily overridden for different deployment environments. This makes it difficult to deploy Texera in various environments (development, staging, production) without modifying configuration files. ## Proposed Solution Allow configuration values in `default.conf` to be set using environment variables. This would enable: - Easy configuration management across different environments - Better containerization support (following 12-factor app principles) - Simplified deployment without modifying code ## Implementation Details The configuration system should: 1. Check for environment variables first 2. Fall back to default values if environment variables are not set 3. Support all major configuration parameters ## Example Usage ```bash export STORAGE_LAKEFS_AUTH_USERNAME="custom-username" export STORAGE_LAKEFS_AUTH_PASSWORD="custom-password" export STORAGE_JDBC_URL="jdbc:postgresql://prod-db:5432/texera" ``` ## Benefits - **Flexibility**: Different configurations for different environments - **Security**: Sensitive values can be injected at runtime - **DevOps friendly**: Easier CI/CD pipeline integration - **Docker/Kubernetes native**: Better container orchestration support ## Related Components - Configuration service - All microservices that read from default.conf - Docker deployment configurations - Single-node deployment setup -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
