service.dockerfile: move DB_SSL check to its own image#1888
Closed
alxndrsn wants to merge 1 commit into
Closed
Conversation
This makes the env check independent of the pgdg container. Logically there's no connection between the check for DB_SSL (which relates to postgres configuration) and the pgdg container (which is specifically making postgres apt repositories available to the final container). This also means that the DB_SSL check will run faster, and when appropriate, fail faster.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This makes the env check independent of the pgdg container. Logically there's no connection between the check for DB_SSL (which relates to postgres configuration) and the pgdg container (which is specifically making postgres apt repositories available to the final container).
This also means that the DB_SSL check will run faster, and when appropriate, fail faster.
What has been done to verify that this works as intended?
Why is this the best possible solution? Were any other approaches considered?
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Does this change require updates to documentation? If so, please file an issue here and include the link below.
Before submitting this PR, please make sure you have:
nextbranch OR only changed documentation/infrastructure (masteris stable and used in production)