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

Support api based migration of data between Quepid's #834

Merged
merged 9 commits into from
Sep 20, 2023

Conversation

epugh
Copy link
Member

@epugh epugh commented Sep 19, 2023

Description

Extend out the apis.

Motivation and Context

I have a Dev version of Quepid, and now a Prod version of Quepid. I have lots of Cases and Books and Users in the Dev version, and I don't have database access to Prod Quepid, so I need to get some data migrated.

How Has This Been Tested?

manual and tests.

Screenshots or GIFs (if appropriate):

Types of changes

  • [] Bug fix (non-breaking change which fixes an issue)
  • [] Improvement (non-breaking change which improves existing functionality)
  • [] New feature (non-breaking change which adds new functionality)
  • [] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • [] My code follows the code style of this project.
  • [] My change requires a change to the documentation.
  • [] I have updated the documentation accordingly.
  • [] I have read the CONTRIBUTING document.
  • [] I have added tests to cover my changes.
  • [] All new and existing tests passed.

@epugh
Copy link
Member Author

epugh commented Sep 19, 2023

Okay, all the little changes weren't getting us there. Adding new import/export endpoints for Books is much better.

@epugh epugh merged commit 8896191 into main Sep 20, 2023
3 of 4 checks passed
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.

1 participant