As a user I would like to be able to store output from a single task plugin or from a combination of task plugins as artifacts for later use and analysis.

[hbooth]

How to store an artifact is not obvious and requires each plug-in that wishes to store data to implement this functionality. In addition, it requires access to/knowledge of MLFlow. Providing built-in functionality that allows for a declarative model for artifacts would address these issues.

Blocked By:

• Implement new API endpoints for browsing and retrieving artifact files #575

Definition of Done

• Extension of Entry Point YAML file to support declarations of artifacts
• Task Engine can validate this new file
• Task engine can produce output appropriate for running a job which appropriately breaks apart the task graph and artifacts
• While running a job the appropriate artifact creation hooks are called which store the artifacts as appropriate
• All new functionality has appropriate tests
• Merged into dev branch

Describe alternatives you've considered
A potential alternative would be to create a "utility" plug-in that implements this functionality that could be called, but it would not address the concerns around MLFlow and other resource access.