Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove hard coded role and db name from init db migration #358

Merged
merged 2 commits into from
Nov 6, 2020

Conversation

splaspood
Copy link
Contributor

Description

The initial database migration currently has a hard coded database name and role. This change removes both.

Why is this needed

This prevents us from deploying tink against a database that happens to utilize a different role or db name.

Checklist:

I have:

  • updated the documentation and/or roadmap (if required)
  • added unit or e2e tests
  • provided instructions on how to upgrade

mmlb
mmlb previously approved these changes Nov 6, 2020
@codecov
Copy link

codecov bot commented Nov 6, 2020

Codecov Report

Merging #358 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #358   +/-   ##
=======================================
  Coverage   24.74%   24.74%           
=======================================
  Files          14       14           
  Lines        1277     1277           
=======================================
  Hits          316      316           
  Misses        940      940           
  Partials       21       21           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a94738e...5d2ea7a. Read the comment docs.

Copy link
Contributor

@mmlb mmlb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@splaspood you need to update the docker-compose.yml so it creates the db

@mmlb mmlb added the ready-to-merge Signal to Mergify to merge the PR. label Nov 6, 2020
@mergify mergify bot merged commit 384fe30 into master Nov 6, 2020
@mergify mergify bot deleted the db-migration-k8s-0 branch November 6, 2020 15:40
@mmlb mmlb removed the ready-to-merge Signal to Mergify to merge the PR. label Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants