-
Notifications
You must be signed in to change notification settings - Fork 4
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
updating job export to work with Helm #89
Conversation
Please find the detailed integration test report here Please find the ci env pod logs here |
job_export.py
Outdated
DB_URL = f"jdbc:postgresql://{DB_HOST}/{DB_DATABASE}" | ||
else: | ||
DB_URL = None | ||
print("DB_HOST or DB_DATABASE is missing. DB_URL cannot be constructed.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we raise an error in this scenario? 🤔 So the application doesn't continue thinking everything is ok, but it has no database. Not sure what we usually do for that in other services.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah if no db exists then the job should throw runtime error
Please find the ci env pod logs here |
Please find the ci env pod logs here |
Please find the detailed integration test report here Please find the ci env pod logs here |
Deployment changes
Our Helm charts utilize eternal secrets to create and manage our secrets. The new Peregrine-dbcreds secret is formatted differently and no longer uses json, so we need to edit the export job so the values can be read via environment variables.