-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export pipeline as JSON feature #267
Comments
Ideas for iteration: MVP: select one plugin, it and all its children are saved as a plugin. Reach goal: allow selection of multiple plugins, assert selections represent a DAG, and save that. |
@sonylomo still you are working on this if not can you pass this issue to me @jennydaman |
@arpit-maurya glad to see you're willing to take this up! The original issue proposed an export to JSON feature. If you would like to take it above-and-beyond, try YAML output instead. Schema: https://github.com/FNNDSC/CHRIS_docs/blob/master/rfcs/2-pipeline_yaml.adoc I'm sure you'll have questions about the spec, so please message me on Matrix. |
@arpit-maurya can I assist with this issue in any way, please let me know. |
Hello @jennydaman, I'm an Outreachy intern candidate and was wondering if this would be a good issue to work on for my initial contribution. |
@oryxwhite this would be a great issue, I have assigned you. |
@jennydaman could you point me towards the endpoint you mentioned that generates a snapshot of the plugin and its children? I've been looking through the API and haven't been able to find it. |
|
Feed view should have a button "Export" which creates a JSON representation of the selected DS plugins as part of a reproducible workflow, aka pipeline. This JSON file can be uploaded to the ChRIS store via POST request. Example:
https://github.com/FNNDSC/CHRIS_docs/blob/master/pipelines/fetal_brain_reconstruction.sh
A corresponding feature in ChRIS_store_ui is supporting import of these JSON representations of pipelines. FNNDSC/ChRIS_store_ui#224
There should already exist an API endpoint which, given a plugin instance ID, saves a snapshot of the plugin instance and its children as a pipeline. Essentially we just need to connect this endpoint to a button.
The text was updated successfully, but these errors were encountered: