[Docs] Create release note guide for Sharing Saved Objects breaking changes #88744
Labels
docs
Feature:Saved Objects
Feature:Security/Sharing Saved Objects
Platform Security - Sharing Saved Objects feature
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:medium
Medium Level of Effort
Team:Security
Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
The Sharing Saved Objects feature (#27004) will introduce a breaking change for existing saved object types.
Before existing object types are converted to become shareable, we will need to regenerate some object IDs to ensure that there are no collisions. When we regenerate these object IDs, consumers of the saved objects HTTP APIs will need to check if object IDs have changed before attempting to manipulate them. We should ensure that a guide is available to help consumers understand the impact of this breaking change.
CC @legrego @rudolf @pgayvallet
NOTE TO SELF: planning on producing this in the new dev docs platform, but that does not appear to be publicly accessible yet. Need to check on that.
The text was updated successfully, but these errors were encountered: