Support dataverse-sample-config

[mheppler]

Just as dataverse-sample-data was added in #83, I would like to see a similar feature such as a hypothetical "dataverse-sample-config" that would easily allow developers to set up any type of feature to their dev or test environments.

[donsizemore]

In Ansible this is generally done by group_vars (see for instance tests/vagrant.yml)

dataverse-ansible can currently install/configure/enable Sample Data, Make Data Count, Custom Metadata, QDR's Previewers, Prometheus, Munin, Grafana, or Dockerized S3 test containers in addition to standard Dataverse components through the use of group_var switches or values. These have been cobbled in organically, generally by request of @pdurbin

What feature did you have in mind?

[mheppler]

All of them?

Sample data has been a huge help developing, as I can see what different files and metadata look like. The most recent UI development challenges have been configuring compute and rsync features.

If we're talking three wishes granted to a front-end developer who is install/configure/enable-ly challenged...

• a library of sample config options that I download and run on an EC2/localhost to set up any and all of the 32 flavors of Dataverse installations (we have somewhere around 60 installations now, but if you boil them down to general "persona types" we could probably provide a handful of config settings that cover a very large majority of those installations)

• a library of sample data files... got that!... but we should definitely continue to add more file types (e.g. dataverse package)

• a library of sample users, various personas that have various permissions to the various dataverses, datasets and files to cover as many common use cases as possible... but all that is for another issue, at another time

[donsizemore]

1. I would welcome say additional group_vars (there is already a defaults/main.yml, a tests/vagrant.yml, and a tests/jenkins.yml which serve different purposes). If you could describe these persona traits in some way that's generically configurable I'll try to make it happen.

2. These files live in https://github.com/IQSS/dataverse-sample-data ; there is also my kludgy custom_sample_data task which simply reads in JSON and/or files from known directories and creates dataverses and datasets accordingly.

3. The test_suite task does this (Darwin's Finches, Spruce Geese and friends). It grabs files from https://github.com/IQSS/dataverse/tree/develop/tests and fires run-test-suite.sh on them.

Tell me more about the compute and rsync workflows? (maybe in separate issues?)