To create this, start with a more basic approach, and work our way up to something more user friendly. One of the points is to NOT make more continuous work for ourselves.
First Potential Steps
- Use a bootstap script
- Load the storage route to the demo data s3 bucket
- Load convert templates and fields to the converttype and configuration collections
- Should be one time load, use a setting file to detect whether already run
Second Potential Steps
This approach would be a big step. Let me know if there is a middle ground.
- Storage route is included by default
- User is able to select what convert template/configurations they want to load
- Configurations could be stored
- In a separate collection and simply copied/merged over
- Simple copy for convert
- Merge for included fields
- In S3 and added to mongo collections
- Similar merge/copy process, but with file data
- Could include a push of the relevant demo data to use with the convert
Third Potential Steps
Include the steps and process as part of functional testing and CICD
- Ensures UI is working correctly
- Can use the demo data for other functional tests and add as needed