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

feat: Reduce manual steps prior to running migration tool #35

Open
wbh1 opened this issue Oct 15, 2022 · 0 comments
Open

feat: Reduce manual steps prior to running migration tool #35

wbh1 opened this issue Oct 15, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@wbh1
Copy link
Owner

wbh1 commented Oct 15, 2022

As reported in #32 and elsewhere, users often run into issues where they did not run an instance of Grafana connected to their destination Postgres database. This causes the migration to fail because Grafana did not create the tables that we're dumping data into.

Possible solutions:

  • Shell script
  • Docker compose
  • Call Grafana's sqlstore migrator as a library to populate the tables ourselves
    • Complicated by the need to match migrations with what's in the existing DB which changes between Grafana versions and we can't dynamically import different versions of a library
@wbh1 wbh1 added the enhancement New feature or request label Oct 15, 2022
@wbh1 wbh1 self-assigned this Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant