Is there a good DevOps method to construct a workflow that creates demo data for a product? This situation is difficult when the app constantly changes. There are a few scenarios to consider.
Either old demo data becomes obsolete in the new build or the old data can be considered corrupted in the new build.
New business logic is introduced which requires interaction with the app for the new data to be formed. You cannot look at the new schema, static rules or old data to derivative/fill in such data.
Program managers have the insider info on what the demo data needs to look like, not the engineers. So the workflow needs to match up during the process, from (build -> test -> deploy) somehow.
One approach is to run tests that have demo data in it. So after the tests were ran, we can extract the data for our demos. But I can see that the tests can be very long and not as instant as importing a csv file. Also the coordination between PMs and engineers seems to be tightly coupled.
Another approach is to start with the new scheme from the repository and generate data from there. But this requires overhead of creating rules for generation which may not be in sync with the logic of app itself.
It seems a top down approach is better, so you generate dynamic data sets per release. Instead of working with a backward compatibility mindset with older static data.
The problem is to keep the app and the data in sync and valid for each iteration, while allowing the PMs and engineers to work in parallel from one another without relying on each other.