-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Config save to S3 #6080
Comments
Backup your metadata database and put the backup file on s3? |
Is there a documentation/recommendation about the best practice of exporting and importing config/dashboards/etc (current state actually)? I can see some scripts in the images such as: dashboard_import_export_util.py, import_util.py, superset_config.py but it would be great if someone can guide me through. Thanks a lot... |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi,
Is it possible or is there a plan for saving the config&dashboards (current state) of superset on S3, like Zeppelin can: https://zeppelin.apache.org/docs/0.8.0/setup/storage/storage.html#notebook-storage-in-s3?
My motivation is keeping the image on kubernetes as basic as possible and keep state elsewhere on cloud.
Superset version
0.27.0
Expected results
Configs are saved on s3.
Actual results
Configs can be exported as YAML.
Steps to reproduce
N/A
The text was updated successfully, but these errors were encountered: