Fixes #37883 - halt if remote DB does not own EVR #984
Conversation
This file contains 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
|
To-do: skip the entire hook if the database is local. |
ianballou
force-pushed
the
37883-halt-installer-evr-permissions
branch
2 times, most recently
from
696bcf1
to
01803e4
Compare
ianballou
force-pushed
the
37883-halt-installer-evr-permissions
branch
from
01803e4
to
174cb40
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Checks if the
postgresuser owns theevrextension. If it does, halt the foreman-installer and report an error with the command to run to fix the permissions.Also check if
postgresis the foreman DB owner. In that case, don't do anything because the migration will succeed.There's no provision if the admin user is called something other than postgres. Should there be?