geoo89
commented
4 months ago Aim: Using the templates stored in this repository, we want to have different deployments that instantiate these templates with different data. For each of these deployments, we would have a separate repository storing the relevant data lists (used to instantiate the templates) with a workflow to compile the deployment into RapidPro flows by pulling the templates from this repository and running the pipeline. This needs:
- [ ] rapidpro-flow-toolkit: https://github.com/IDEMSInternational/rapidpro-flow-toolkit/issues/126
- functionality to convert data sheets to (nested) json
- functionality to read one or multiple content indices, extract and merge the contained data sheets into a single json, and save it
- functionality to compile the metadata about the data sheets contained in the content index sheet as a json
- [ ] rapidpro-flow-toolkit: https://github.com/IDEMSInternational/rapidpro-flow-toolkit/issues/127
- functionality to read a collection of data sheets in the aforementioned json formats, to
- [ ] deployment repos: github action + config to pull data from existing spreadsheets, compile this data into json using aforementioned mechanism, and commit a snapshot of this data
- [ ] deployment repos: github action + config to run the pipeline using the data on the deployment repo with the templates from this repo, and product RapidPro flows.
Combine the model of a data list with the actual content into a single json format. Enable the format to have data that cuts across multiple sheets, multiple files and even multiple folders.