Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backend] Currently There Is No Validation Regarding the Existence of the Environment Variable values #247

Open
sonadztux opened this issue Jan 21, 2022 · 0 comments
Labels
backend bug Something isn't working

Comments

@sonadztux
Copy link
Collaborator

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/

@sonadztux sonadztux added bug Something isn't working backend labels Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant