As an integration-test-writer, I should be able to add file based resources / light-modules (YAML primarily).

Use cases

• Resources module / resources-app
• generally light-development

The "challenge"

Since the webapps to test against run on a docker image and the tests are executed from another (virtual) network location, we need a mechanism to transfer the files to the magnolia.resources.dir of the webapps.
In a 1st quick discussion about the topic, apchelintcev was proposing to have a specific servlet for this purpose on the test-webapps.

 Possibilities:

• Uploading (and cleaning up) YAML files to resources workspace (imagine to reuse MagnoliaRestClient); maybe auto-wrapping "real" YAML files into mgnl:resource node bootstraps?
• Consider adding folder support for Fixture/Cleanup utilities?
• Mounting an external directory for light-module directory, and e.g. have a JUnit5 extension dynamically add/remove aliases/symlinks.

Timebox: 5