You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Options:
-p, --path TEXT Path to a single ZIP file [required]
-u, --username TEXT Specify the user name to assign dashboards to
[required]
--help Show this message and exit.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
I have searched Superset docs and Slack and didn't find a solution to my problem.
I have searched the GitHub issue tracker and didn't find a similar bug report.
I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
The text was updated successfully, but these errors were encountered:
Bug description
Hello,
Option for file could be the same for superset export-dashboards / superset import-dashboards
Actually :
In https://github.com/apache/superset/blob/master/superset/cli/importexport.py
"-f" is used to define a file for :
export_dashboards :
export_datasources :
(and 2 legacy :
)
"-p" is used to define a file for :
import_dashboards
import_datasources
(and 4 legacy :
)
"-p" should be used everywhere, like superset fab export-roles
Best regards
How to reproduce the bug
superset export-dashboards --help
Usage: superset export-dashboards [OPTIONS]
Export dashboards to ZIP file
Options:
-f, --dashboard-file TEXT Specify the file to export to
--help Show this message and exit.
superset import-dashboards --help
Usage: superset import-dashboards [OPTIONS]
Import dashboards from ZIP file
Options:
-p, --path TEXT Path to a single ZIP file [required]
-u, --username TEXT Specify the user name to assign dashboards to
[required]
--help Show this message and exit.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: