Suggestion: Provide exportable config for this plugin

Thanks for the suggestion @datawench. There is currently import/export functionality, though it does not use the config system since that is not where the data is stored.

You can find these options at Extend -> Documentation -> Export ( or Import). You should be able to take the file created/downloaded from Export and upload it on a different (or the same) site/environment to (re)populate all of the data entered through this module.

Note that it will overwrite all existing data (records that have the same IDs) though it won't delete newer records on the target environment that don't have a corresponding/matching ID in the import file.

Don't mean to be a noodge, but might you consider a drush command? Again, my concern here is with deployment automation. I offer here a possible addition. The idea is that its export() would generate a file that you could commit to the repo, and the CI/CD builder could execute the import().

I would be happy to include a drush command, esp. since you provided it. Thanks for that. I was more focused on the config aspect of the request when I closed this.

Can you create an MR for this?

This feature has been merged and will be included in the next release. It will also be available in the next roll of the dev release.