I have an existing project and would like to dupli...
# orm-help
j
I have an existing project and would like to duplicate my demo data to a new service in order to test some schema changes without having to deploy them to my only service. Is there a simple way to duplicate an existing Prisma dev service, or do I need to manyally
prisma init
a new service? Is there a way to carry over the data that I have in an existing service? Or is there some completely different workflow I should actually be looking at
n
The pieces are there, with `prisma export`/`prisma import` and service stages. Currently, there is no simple command that combines those pieces into a unified "clone service" feature. Could you actually raise this as a feature request here: https://github.com/prismagraphql/prisma? I would love to collect further feedback here to discuss current approaches and think about how this can be improved.
j
Alright, thanks for the answer. I’ll open an issue when I have the time, thanks!
Is there anything else I should know about the intended development flow when it comes to schema changes during maintenance or feature development?
I guess people generally just spin up as many services as they feel they need
n
Yup that is already a useful tool here. Generally, we are looking to improve such workflows. There is an ongoing effort to do so in #migrations. There is an open issue to improve documentation around multi stage workflows here: https://github.com/prismagraphql/prisma/issues/2732 here's an example for a generally useful pattern in this context - deploy Prisma to CI: https://github.com/prismagraphql/prisma/tree/master/examples/travis
Lastly, you can think about how seeding can help you for multi stage workflows: https://github.com/prismagraphql/prisma/issues/2618
j
Great info, very interesting
Cheers!
n
Sure! 🙂 Thanks for starting this discussion. Curious to hear your thoughts on the resources I shared. Also would love to hear other's input here!