We are looking for a way to script schema migrations and seed data.
The use case:
Parse is running on a local development machine where schema changes and seed data are developed and / or modified from a previous state.
Once development changes are finished, we would like to be able to automate the process of applying these schema and seed data changes to other development and test environments and also the production environment without risk of human error and the time spent using tools like the dashboard.
We don’t want to open field and / or class creation in production, so this can’t happen dynamically through application usage.
This process is typical in a lot of application stacks like rails, dotnet, etc. Migration files that are generated or written and then run sequentially against other environments.
Am I thinking about this problem correctly? Redirect me if there’s a different way to solve this problem with parse or let’s talk about data migrations in parse.
Conceptually a tool could be written that enumerates the schema using a master key and can apply this schema to another instance of parse. Give it a list of seed tables and it could track rows for these tables as well. This gets more complicated if you want to script diffs because you can’t recreate a schema that already exists. Would need to identity existing tables and build an appropriate schema update. Does anything like this already exist?