Adding a workaround to connect to the DB directly for migrations #913
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
…pgbouncer which messes up permissions
bgvozdev
approved these changes
Nov 15, 2021
| }, | ||
| "production-migrate": { | ||
| "dialect": "postgres", | ||
| "use_env_variable": "PG_DATABASE_URL", |
There was a problem hiding this comment.
So the difference here is in the database url, right? DATABASE_URL goes through the PG Bouncer and PG_DATABASE_URL goes directly to postgres, correct?
There was a problem hiding this comment.
This is just a workaround for now until pgbouncer permissions are fixed with the sidecar.
thombergs
approved these changes
Nov 16, 2021
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.
Pgbouncer sidecar seems to change the permission model on the DB, setting it as the user itself instead of the role. Micros data team needs to look further into this, but in the meantime I've found a workaround of using
PG_DATABASE_URLto connect directly to the repo - circumventing pgbouncer - just for the sequelize migration.