fix: Adding v0 import/export fields to dashboard metadata schema #13425
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
We see errors editing the metadata for dashboards that were imported using the v0 import/export feature. I'm adding those fields to the DashboardJSONMetadataSchema so we don't see those errors on validation. I'm adding these fields to the schema instead of removing them because the v0 import/export feature uses them.
I tested this change by editing a chart with these fields, let me know if there's anything else to test with this change.
TEST PLAN
I tested editing a chart that had these fields in the dashboard
json_metadata
.ADDITIONAL INFORMATION
Unknown Field
error when editing dashboards withremote_id
andimport_time
#10742@betodealmeida @dpgaspar @serenajiang