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

Migrate PortabilityJob, AuthData, and job stores to the new directory structure #113

Merged
merged 4 commits into from Feb 2, 2018

Conversation

rtannenbaum
Copy link
Contributor

Make portability-core call PortabilityJob and AuthData in the new directory structure, and deprecate the old versions.

Also replace PersistentKeyValueStore with JobStore, and replace the following impls:

  • GooglePersistentKeyValueStore -> GoogleCloudDatastore implements JobStore
  • InMemoryPersistentKeyValueStore -> InMemoryKeyValueStore implements JobStore

Tested locally with encryption flow on and off.

…ectory structure, and deprecate the old versions.

Also replace PersistentKeyValueStore with JobStore, and replace the following impls:
- GooglePersistentKeyValueStore -> GoogleCloudDatastore implements JobStore
- InMemoryPersistentKeyValueStore -> InMemoryKeyValueStore implements JobStore

Tested locally with encryption flow on and off.
Copy link
Collaborator

@holachuy holachuy left a comment

Choose a reason for hiding this comment

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

This looks good, A couple of general thoughts

  1. Is it worth moving to the new PortabilityJob in this PR?
    if no, then
  2. Can we name OldPortabilityJob - LegacyPortaiblityJob

@rtannenbaum
Copy link
Contributor Author

I'd prefer to move to the new PortabilityJob in a separate PR, this one already has a lot of changes and I haven't thought too much about how to port over yet.

I just updated the name to LegacyPortabilityJob, good idea

Also, FYI this is branched off of the other branch with the JobStore changes, so after this I'll send another PR to merge the whole thing into master

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.

None yet

2 participants