Use a start hook instead of overriding the entire run-postgresql script#8
Merged
bdunne merged 2 commits intoManageIQ:masterfrom Feb 7, 2018
Merged
Conversation
We didn't use it and the new image has included conf built in at /opt/app-root/src/postgresql-config/
This utilizes the startup hooks built into the SCL PG image to make our user a SUPERUSER. This was really all the custom run-postgresql script was accomplishing This also fixes a bug which was caused by us calling a function which had been removed from the base image. https://bugzilla.redhat.com/show_bug.cgi?id=1540957
gtanzillo
approved these changes
Feb 6, 2018
Member
|
@bdunne same with this one, GreggT approved. As this is for a blocker issue, looking for merge. |
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
4 participants
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 utilizes the startup hooks built into the SCL PG image to make our user a SUPERUSER.
This was really all the custom
run-postgresqlscript was accomplishingThis also fixes a bug which was caused by us calling a function which had been removed from the base image.
https://bugzilla.redhat.com/show_bug.cgi?id=1540957