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

Write test migration script for us for initial DS migration test. #18

Open
tublitzed opened this issue Nov 13, 2019 · 1 comment
Open
Assignees
Labels
5 Estimate - m - This is a small change, but there's some uncertainty.

Comments

@tublitzed
Copy link
Contributor

tublitzed commented Nov 13, 2019

This can be rough for now, as we're testing a single sync user first. This will be for use with our initial test for migrating one sync user.

  • Script should be able to point to existing Sync DB (dev is fine), and pull data by sync id (or some identifier that we can get with sync id).
  • Should then be able to insert same data into Spanner dev DB.

As long as the DB hosts are easily configurable, we should be able to eventually modify this to run against stg/prod as we refine.

@tublitzed tublitzed added the 5 Estimate - m - This is a small change, but there's some uncertainty. label Nov 13, 2019
@tublitzed tublitzed added this to Backlog: Misc in Services Engineering via automation Nov 13, 2019
@tublitzed tublitzed moved this from Backlog: Misc to Prioritized in Services Engineering Nov 14, 2019
@jrconlin jrconlin moved this from Prioritized to Active in Services Engineering Dec 9, 2019
@jrconlin jrconlin moved this from Active to In Progress in Services Engineering Dec 10, 2019
@tublitzed tublitzed moved this from In Progress to Prioritized in Services Engineering Dec 16, 2019
@tublitzed
Copy link
Contributor Author

De-prioritized in favor of this one.

@jrconlin jrconlin moved this from Prioritized to Active in Services Engineering Dec 17, 2019
@tublitzed tublitzed moved this from Active to Prioritized in Services Engineering Dec 17, 2019
@tublitzed tublitzed moved this from Prioritized to Scheduled in Services Engineering Jan 2, 2020
@jrconlin jrconlin moved this from Scheduled to In Review in Services Engineering Jan 8, 2020
@tublitzed tublitzed moved this from In Review to Done in Services Engineering Feb 4, 2020
@tublitzed tublitzed moved this from Done to Archived in Services Engineering Feb 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5 Estimate - m - This is a small change, but there's some uncertainty.
Projects
Development

No branches or pull requests

2 participants