GitHub user gaeljw added a comment to the discussion: Best Practices for
Storing Superset Dashboards in Git
I'm dumping automatically the result of Superset export ZIP into a Git
repository for traceability/history/indexation and came upon this thread.
I'm facing a weird behaviour where some IDs change in the dashboard exports
even though nothing changed in the dashboards themselves. Is this expected?
This makes the "history" feature less interesting due to commits with "fake
changes".
Here's an example of such a "fake changes/diff" that I observe in a dashboard
yaml export:
```diff
parents:
- ROOT_ID
type: TABS
- CHART-VAEM8ECF:
+ CHART-FU08RIS4:
children: []
id: CHART-VAEM8ECF
id: CHART-FU08RIS4
meta:
chartId: 1347
height: 50
...
uuid: 9dfdd1dc-5808-4c33-bb7d-f46712891c58
width: 4
type: CHART
- CHART-OYGMTK86:
+ CHART-4J8783D4:
children: []
- id: CHART-OYGMTK86
+ id: CHART-4J8783D4
meta:
chartId: 1333
height: 50
```
GitHub link:
https://github.com/apache/superset/discussions/30190#discussioncomment-16190197
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
