[CM] Migrate visualization annotation graph to saved_object_content_storage
#167421
Assignees
Labels
enhancement
New value added to drive a business result
impact:medium
Addressing this issue will have a medium level of impact on the quality/strength of our product.
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
Comments
Dosant
added
the
Team:Visualizations
|
Pinging @elastic/kibana-visualizations (Team:Visualizations) |
stratoula
added
enhancement
Dosant
added a commit
that referenced
this issue
Sep 28, 2023
## Summary Close #167152 Log a warning instead of throwing an error in `saved_object_content_storage` when response validation failed. We decided to do this as a precaution and as a follow up to an issue found in saved search #166886 where storage started failing because of too strict validation. As of this PR the saved_object_content_storage covers and this change cover: - `search` - `index_pattern` - `dashboard` - `lens` - `maps` For other types we agreed with @dej611 that instead of applying the same change for other types (visualization, graph, annotation) the team would look into migrating their types to also use `saved_object_content_storage` #167421
drewdaemon
added a commit
that referenced
this issue
Oct 14, 2023
…ent_storage` (#168520) ## Summary Close #167421 --------- Co-authored-by: kibanamachine <[email protected]>
dej611
pushed a commit
to dej611/kibana
that referenced
this issue
Oct 17, 2023
…ent_storage` (elastic#168520) ## Summary Close elastic#167421 --------- Co-authored-by: kibanamachine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a follow up to #167152 #166919, we should migrate the remaining saved object based content types to use the common util https://github.com/elastic/kibana/blob/main/packages/kbn-content-management-utils/src/saved_object_content_storage.ts util
This will soften the response validation for these #167152 as we did for other types. This should also help with any other future common changes for simple saved object based storages.
Alternatively, the response validation can be removed manually by replicating the same patten as the
saved_object_content_storage.tscc @dej611
The text was updated successfully, but these errors were encountered: