-
Notifications
You must be signed in to change notification settings - Fork 113
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
Allow saving pipeline to svg and png #638
Comments
kedro viz --export
commandkedro viz export
command
kedro viz export
commandkedro viz export
command
Hi @danielgafni! Thanks for raising this feature. I wanted to find out what you would expect to happen when you've run this command. Is it that you're trying to "screenshot" a version of the pipeline? |
Yeah, something like this. Could be useful for automatic documentation updates (for example, push the image to Confluence). |
Hi @danielgafni. Thank you for raising this. We're going to close this issue for now and will certainly circle back in the future if additional demand for this arises. In the meantime, please note that you can download the pipeline visualization from the Kedro-Viz interface (though that's a manual process, not programatic). |
kedro viz export
commandkedro viz export
command
Given that we already have
and work out the correct format from the file extension. If no extension is given then use json as we do currently. I'm not sure how easily we will be able to directly access the export functionality from the backend side though. Currently it's all buried a bit in |
kedro viz export
command
Agree on the implementation thoughts. And yes, I'm not sure how we'd get the contents of |
More desire for this from users: |
Description
The
kedro viz export
command would allow visualizing the pipeline DAG from the command line.Options:
--pipeline
pipeline to export--format
[png, svg]--resolution
if png format is used--output
output pathContext
This can be used in:
CI pipelines
pre-commit hooks (always up to date project documentation)
And other automation.
Include labels so that we can categorise your feature request
The text was updated successfully, but these errors were encountered: