Is your feature request related to a problem? Please describe.
The backend stack requires some values to be stored in environment variables in order to function properly. In the development process, this refers to access to the .env file, while in production the env variable value is stored and accessed from the Kubernetes deployment YAML file.
The problem is there are some values that have to be set manually and these are prone to be forgotten when deploying to production, causing some functionality to not work.
Describe the solution you'd like
There needs to be a mechanism to validate whether all environment variable values have been set or not, if some are not set then the application throws a panic and should not run. Simple workable solutions can refer to the following article (not limited, feel free to explore more): https://www.loginradius.com/blog/async/environment-variables-in-golang/
Is your feature request related to a problem? Please describe.
The backend stack requires some values to be stored in environment variables in order to function properly. In the development process, this refers to access to the .env file, while in production the env variable value is stored and accessed from the Kubernetes deployment YAML file.
The problem is there are some values that have to be set manually and these are prone to be forgotten when deploying to production, causing some functionality to not work.
Describe the solution you'd like
There needs to be a mechanism to validate whether all environment variable values have been set or not, if some are not set then the application throws a panic and should not run. Simple workable solutions can refer to the following article (not limited, feel free to explore more): https://www.loginradius.com/blog/async/environment-variables-in-golang/