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
Is your feature request related to a problem? Please describe.
Dashboards currently only exist in superset. They're crafted in the UI and the queries are autogenerated.
There is no way to write dashboards as code, and no way to do actual version control. Unfortunately.
However there is a way to export dashboards, and there is a way to import them later.
The output is a collection of yaml files that are not meant to be read by humans.
Describe the solution you'd like
Set up a process as part of cht-sync that does automatic backups for all dashboards and stores them to be available for backups.
If there is an automated way of pushing config to the instance, backups should be part of this process.
Describe alternatives you've considered
Automatic backups can be outside of cht-sync but should be ready out of the box anyway.
The text was updated successfully, but these errors were encountered:
…et dashboard export (#154)
This reusable GH action will store a Superset export within the repo that triggers the action.
Can be further parametrized if desired, but for now:
only supports saving in the current repo
saves on hardcoded path
#142
Is your feature request related to a problem? Please describe.
Dashboards currently only exist in superset. They're crafted in the UI and the queries are autogenerated.
There is no way to write dashboards as code, and no way to do actual version control. Unfortunately.
However there is a way to export dashboards, and there is a way to import them later.
The output is a collection of yaml files that are not meant to be read by humans.
Describe the solution you'd like
Set up a process as part of cht-sync that does automatic backups for all dashboards and stores them to be available for backups.
If there is an automated way of pushing config to the instance, backups should be part of this process.
Describe alternatives you've considered
Automatic backups can be outside of cht-sync but should be ready out of the box anyway.
The text was updated successfully, but these errors were encountered: