At the moment a lot of the behaviour of the pipeline is hard-coded here including the meshes that are produced, preparation and upload of the files.
It would be an improvement to control the behaviour for different environments/settings, ideally with environment variables.
For instance in a development setting it would save some time to only run one mesh at a time.
Or the pipeline might be deployed in a setting where we don't need to upload/transfer the files, so we might want to switch on/off those steps.
Related to this is automatic discovery/processing of mesh configs and #4
At the moment a lot of the behaviour of the pipeline is hard-coded here including the meshes that are produced, preparation and upload of the files.
It would be an improvement to control the behaviour for different environments/settings, ideally with environment variables.
For instance in a development setting it would save some time to only run one mesh at a time.
Or the pipeline might be deployed in a setting where we don't need to upload/transfer the files, so we might want to switch on/off those steps.
Related to this is automatic discovery/processing of mesh configs and #4