fix: Add postgres envvar to dev.env #1524
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The postgres envvar is missing in the dev.env, and this results in postgres' health check failing as it uses these envvars. this makes the health check default envvar like
POSTGRES_USER
to blank string. For some reason it is not enough just to specify them in the environment section of the docker compose file so add these to dev.env just like deploy.envSummary by Sourcery
Bug Fixes: